Module · Shop
Stock is per colour,
which is the whole difference.
Sell from your own site with real variants, real stock counts, and the payment methods people where you are actually use. Orders arrive with the address in them and a status you move by hand.
Example product — stock is per variant, not per product
Example — four methods, three of them not a card
How people pay you
Three kinds, and only one of them is a card.
Payment methods are yours to define, not a fixed list. Each one has a label, instructions the customer reads, whether it needs a reference number, and a fee if it carries one.
That matters because in most of the world the common ways to pay are not a card. A shop that only offers Stripe is a shop that loses the order at the last step.
The order
It arrives with the address in it, and a status you move yourself.
Four states, moved by hand, because a small shop knows things a workflow engine does not.
Example — confirmed, not yet sent
Example orders
Each line remembers the product
An order line stores the name, the variant, the image and the price as they were when it was placed — so renaming a product next month does not rewrite last month's orders.
Offline revenue counts when you say
For a transfer or cash on delivery you choose whether the money counts when the order is placed or when it settles. Both are defensible; guessing for you is not.
A reference, where one is needed
Methods that need a transfer reference ask for one and hold it against the order, so matching a payment to a parcel is looking rather than remembering.
Example stock view
Stock
Counted per colour, and it tells you before you notice.
Stock is counted per variant, so Olive running out does not take Sand down with it. There is a low-stock view rather than you noticing at the wrong moment.
When a variant sells out, people can ask to be told when it is back. The waitlist records who asked and whether they have been notified — which is the most valuable list in a small shop and the one usually kept in somebody's head.
How people find things
Filters that mean something, because you defined them.
Attributes are yours — material, shape, size, whatever your products actually vary by — and each can be marked filterable.
Example — the last one is information, not a filter
Your attributes, not a fixed set
A key, a label, and the values it can take. Mark one filterable and it becomes a filter on the storefront; leave it off and it is just information on the page.
Collections
Group products however you sell them — a season, a category, a table at the front of the shop. A product can sit in more than one.
Shipping zones with real numbers
Each zone has a fee and an expected time, and there is a free-shipping threshold if you want one. The customer sees the number before they commit, not after.
How you get it
It is already on when you get the dashboard
This one is not on a checkout page, and you do not have to ask for it. Module flags are set while your dashboard is being built — if the site needs it, it is switched on before you ever log in. Nothing extra on your plan, and nothing to request.
If your site sells products, shop is switched on during setup with your products, variants and payment methods already loaded. The afternoon that takes is ours, not yours.
Before you start
What this does not do, said now rather than later.
Helm is not the payment processor
Card payments go through Stripe on your own account. For transfers and cash on delivery Helm records what was agreed and holds the reference — the money never touches us.
No warehouse or multi-location stock
One stock number per variant. If you are counting the same product across three shops, this is not the system for that.
No automated shipping labels or courier integration
Zones, fees and expected times are yours to set. Booking the courier is still something a person does.
Getting started
Tell us what you sell, and how people where you are pay for it.
Switched on per account rather than bought. Plans start at $20 a month.