Dukachap / Trader guide
Set up your online store
Set up a branch, store, products and credentials, then check your storefront before launch.
Your account starts with a Main Branch. If you need another location, create it under Branches first. Each branch has its own stock; a store currently uses exactly one branch for prices, availability and fulfilment.
In Stores, enter a store name, URL slug and branch, then select Create store. The store starts as a draft. You can open it from the list to manage its profile, access and orders. A Storefront endpoint and its keys also belong to this one store; selecting all branches with one credential is not available yet.
Open Catalogue → Products and create a product or open an existing one. Set its selling price and, if you track stock, add stock to the branch selected for your store. A published product without a price appears with no price in the API; stock availability comes from that branch.
In the product's Storefront visibility section, turn on Publish to storefront, tick the store where it should appear, and save. On a new product, this is part of Create product; on an existing product, select Save store visibility. The product must also be active. Publishing it for one store does not publish it for another.
Open your store from Stores and stay on Profile & access. Add a slogan, description, location, logo and favicon, then select Save profile. Light and dark image variants are optional; an empty variant falls back to the main image.
The Orderstab on the same page shows this store's orders after shoppers begin checking out. Store status is managed from the Stores list; select Activatewhen you're ready to launch.
Payments come configured with Dukachap. Open your store from Stores and find Receive payments.
- Choose M-Pesa till, paybill, phone or bank account.
- Enter the destination’s account details and save.
- Check that the saved destination is correct before taking payments.
The payment gateway is managed by Dukachap. Keep your destination details private; they are not exposed in your public storefront.
Sign in as an owner and open API keys → Create API keys. Choose the store, choose Test or Live, and name the group. Keep Storefront endpoint enabled. Include a Publishable key for catalogue and cart features; include a Secret key if your site handles checkout, orders, customer accounts or AI. An endpoint needs at least one matching key.
Each item has its own permissions. A request can do only what both the endpoint and the key allow. For example, products:read must be present on both to list products. Keep the endpoint and keys in the same store and environment; a Test key does not pair with a Live endpoint.
After selecting Create, copy the Storefront endpoint token, Storefront configuration URL, Storefront request base URL and each enabled key from the dialog. The configuration URL contains the full relay token and belongs only on your server. The request base URL contains a short prefix; requests also send the full token in X-Dukachap-Relay and a matching key in X-Dukachap-Key.
These values are shown once. Save them securely before selecting Done, which closes the dialog and returns to the API key list. If you lose a value, create replacement credentials; the original plain token or key cannot be displayed again.
Give your developer the saved endpoint details and keys securely, along with the developer guide. The included storefront uses the full configuration URL as STOREFRONT_GATEWAY_URL on its server, plus DUKACHAP_PUBLISHABLE_KEY and, when needed, DUKACHAP_SECRET_KEY for the same store and environment.
The server calls the request base URL with paths such as /storefront/products and sends the full relay token and key as headers. Keep the relay token and secret key out of browser code. The publishable key has narrower permissions, but a call through this endpoint still needs the private relay token, so your website should send it from its server.
Ask your developer to call /storefront/me, /storefront/settings and /storefront/productsthrough the issued endpoint. The first confirms the store, environment and permissions; the second checks the profile; the third checks product visibility. If a product is missing, review its active status and Storefront visibility selections. If its price is empty or availability is wrong, check its price and stock for the store's branch.
Test carts, checkout and payments in a configured sandbox before taking live orders. Then set the store to Active on the Stores page and turn off Coming soon on the store page when the website is ready for shoppers. Test and Live credentials are separate; create a Live endpoint and matching Live keys for live traffic.
On the store's Profile & access page, turn on Enable customer signup & sign in if shoppers should have accounts and order history. Your website must provide the signup and sign-in screens. Give its server a secret key, and an endpoint, that both carry the needed customers:read and customers:write permissions; guest checkout remains available. The customer identity belongs to your merchant account; sign-in sessions and order access are bound to the store used.
The store's Coming soon & invite codes card lets you turn on the coming-soon setting and select Generate invite code. Dukachap chooses a short word and three random digits, such as BLOOM-200. The code stays visible on this card so you can copy and reuse it. The card shows how many times it has been used. A code only unlocks the store it belongs to, and you can revoke it from the same card. Your website reads the coming-soon setting and uses the verification endpoint to decide whether to show the shop.
To collect newsletter or waiting-list emails, open Subscribers, create a group for this store, and give its slug to your developer for the signup form. The group page shows the addresses collected for it.
Your customer-service, operations and marketing agents are in the workspace. Developers can add storefront AI tools using a server-side secret key and an endpoint that both carry ai:write. See the AI endpoints in the developer guide for the available calls.
