E-commerce: your store

Eight steps — your store, outlets, products, payments, returns, delivery, the POS, and a review. Each step is saved when you go on, so you can leave and come back where you were. Nothing is built until you press Set up my store on the review; then it takes about a minute, and you can leave the page while it runs.

A store is still a normal project: you can build your own models next to it, link them to products, orders or customers, and use automations, PDF templates and the public API as in any app.

• A store sells: the POS opens at a store, and a register (till) is made at each one.
• A warehouse keeps stock and sends it on to stores with a stock transfer.
• Each needs a short code (MAIN, DHK-1) — it’s printed on receipts.

After setup, outlets are records of their own on the Outlets page: add, rename or close them there.

A sale can be paid several ways at once (part cash, part card); cash shows the change to give.

Switch on Deliver orders for orders taken by phone or by hand that go to the customer: they get a delivery address and a shipping charge from the list you set. Pick the couriers you use (in Bangladesh: Steadfast, Pathao, RedX — or a courier without an API, typed by hand) — an order’s page then has Send to courier, which books the parcel with your own courier account and follows it. You connect each account after setup, on Delivery settings: see Your courier accounts.

The review shows each step in one line; Needs a look marks a step with something missing. Press Set up my store. If the setup can’t finish, nothing of it is kept and the wizard says why — fix it and set up again.

Pages for things you switched off stay hidden until you switch them on in Store settings.

The website rule lives on the Categories list endpoint (API → Endpoints): a filter that leaves out what’s inactive on the website, sorted by Order on website. Change either there if your site needs something else. Like the rest of the store’s fields, these can be relabelled or hidden but not removed; add your own beside them.

• Put a product in collections from its form: Collections, under Category and Brand.
• Or from the collection’s page: its Products tab lists what’s in it. Add existing picks products already there (they keep their other collections); Remove on a row takes that product out — the product itself stays. Add product makes a new one already in it.
• Collections are for your website only — the POS keeps to its categories.

On your website, the Collections list endpoint leaves out the inactive ones, sorted by Order on website, and a collection’s products are the Products list with ?collections=<its id> (API → Endpoints). See also tabs that add existing records.

• Tax rates holds your taxes (VAT 15%…) with a Status and one Default. A product with no tax of its own is charged the default rate.
• A category’s Tax / VAT goes to every product in it, and a product moved to a category with a tax takes it. A new product with no tax takes its category’s.
• A variant always has its product’s tax — it can’t be set on its own.
• Price after tax is worked out for you from the price and the tax the till would charge, by your store’s tax mode: tax added on top, tax already in the price (it equals the price), or no tax. Edit a rate, the default or the tax mode and every price follows.
• Switch a tax to Inactive and it comes off every category, product and variant that had it (their price goes back to the bare price). Switch it back to Active and exactly those get it back.
• A tax in use can’t be deleted: you’re told how many products, categories and variants have it, and Replace with… moves them all to another active tax first.

These rules run as System automations (Automations): you can switch each on or off and read what it did in Runs, but not edit or delete it.

• Give a product its options (Size: S, M, L · Colour: White, Navy) and save: its variants are made from every combination. Add a value later and the new combinations appear; take one away and those variants stop selling — they’re never deleted, since orders and stock name them.
• A product without options has one variant of its own, hidden, that follows the product’s SKU, barcode and status.
• A variant can have its own SKU, barcode and price; an empty price is the product’s. Its tax is always the product’s.
• SKUs and barcodes are one item’s each — saving one that another item has is refused, naming who has it.

1. Requested — a return was asked for. Approve it, or Reject it.
2. Approved — you agreed to take it back. Mark received when the items arrive (or Reject).
3. Received — the items are back. The refund is paid from here, which marks it Refunded.
4. Refunded or Rejected — Close it when it’s all done.

Each courier is your own merchant account with them: you open it, you paste its keys into Mint, the courier bills its delivery charges to you and pays the cash it collects straight to you. Mint never holds that money. Keys are kept locked away — Mint only shows whether each one is saved — and never go to your website or to an AI.

1. Open a merchant account with the courier, if you haven’t one (each card links to its sign-up).
2. Paste the keys from the courier’s own panel into the card, then Save & test. Mint asks the courier with them and says what came back — “Connected — balance ৳1,240”, or what’s wrong.
3. Pick the courier’s settings: the pickup store (from your account), delivery type, the weight to use when an order doesn’t say.
4. Copy the webhook address (and secret) from the card into the courier’s webhook page, so it tells Mint where each parcel is. Mint also asks about quiet parcels every 15 minutes, so nothing is missed if a call gets lost.

1. In Steadfast’s dashboard, open API and add a key named “Mint”. Paste its API key and secret key into the Steadfast card and press Save & test.
2. Open Steadfast’s Webhook page. Paste the Callback URL and Auth token from the card and press Save webhook. Steadfast keeps one address per account, so this replaces any address that’s there now. If you’d rather use Steadfast’s Generate button, paste the token it makes into the card’s “Or paste the token Steadfast generated” box.

1. In Pathao’s merchant panel, open Developer API → Merchant API Credentials (press Generate Credentials if it’s empty). Paste the client id and client secret, and the email and password you sign in to Pathao with — Mint uses them only to sign in to Pathao, and keeps them locked away.
2. Pick the pickup store, delivery type (normal or on demand) and what you send (parcel or document).
3. In Developer API → Webhook Integration, paste the Callback URL and secret from the card, choose All events, press Add Webhook and use Pathao’s test button.

1. In RedX’s merchant panel, open Developer APIs → Configuration and request a token (the sandbox token is on the same page — use it with Mode: Test). Paste it and press Save & test, then pick your pickup store.
2. In Developer APIs → Webhook, paste the address from the card and press Enable. RedX signs nothing, so the secret is inside the address — keep it private; New secret makes another one.

Turn on Manual courier and list the couriers you use, one per line: a name, then | and its tracking link with {tracking} where the code goes, if it has one — Sundarban | https://…/track/{tracking}. When you send an order, pick the courier and type the tracking code from their slip. Move the parcel on with Update status on the order; marking it delivered records the cash collected, just as with the other couriers.

Cash with couriers is what couriers have collected for you and not paid out yet, in all and by courier. Search by delivery, invoice, tracking code or phone; tick delivered parcels to mark them paid out. Two emails come with the store, switched off — “Tell the customer it’s on the way” and “…it’s delivered” — turn them on in Automations.

With Steadfast connected, Check the buyer in Send to courier shows how parcels to that phone number have gone across Steadfast: usually takes them, takes some and refuses some, or often refuses — then consider asking for payment first. “Not known” means too few parcels to tell. The answer is kept for a day; Steadfast limits checks by how many parcels you book.

• Orders, payments, returns, stock levels, stock movements, shifts and store credit are made by the store, not with an Add button. Their own fields you added can still be edited.
• Fields the store works out — stock on hand, an order’s totals, paid and refunded amounts, a customer’s credit — show greyed out in forms and can’t be imported or changed in bulk.
• In Models, the store’s own fields can’t be removed or turned into another kind, and its models can’t be deleted. Rename their labels, add your own fields and links, change the layout — that’s all fine.

Switching something on shows its pages at once (coupons, brands, shifts…). Switching it off hides them — but not while it still holds what it made: variations stay on while a product has several variants, store credit while a customer has credit, shifts while one is open.