Guides

Start here

What Tillstack isQuickstartAuthentication

Getting data in

How data gets inSync API referenceYour payment providerReconciliation

Building on it

Terminal integrationSales, returns, shiftsCatalog and stockInventory ledgerCatalog layout on devicesProduct picturesReportsWebhooksEmail and EngageRunning without our UI

Using the console

Operator portalMerchant guide

Reference

Sandbox, OpenAPI, PostmanErrors and limitsSecurity

Using the console

Merchant guide

The merchant owner (or manager) is the person who actually sets the shop up and runs it day to day. The operator provisions the business and its terminals; after that, the merchant works alone. The console is built around that.

People and what each sees#

Role Menu Can change
Owner Everything, including My business (profile, receipt, staff, branches, devices, branding) Everything
Manager Overview, Sales, Catalog, Stock, Reconciliation, Reports, My business (read only; no Staff or Branding) Catalog and stock
Stockkeeper Overview, Catalog, Stock Catalog and stock
Cashier Overview, Sales Nothing in the console (they sell on the terminal)
Operator / reseller / platform staff see all merchant screens plus Merchants, Terminals and network reports.

The API is the real gate (a request outside a role's scope is refused); the console hides what a role cannot use (composables/access.ts). Note the API lets every role read sales and reports; the console only hides them. Tighten the API if that matters.

My business (/business)#

  • Profile: name, address, phone, email, tax ID (GET/PUT /v1/organizations/{id}/profile). MID is read only.
  • Receipt: a footer line, with a live preview. The business name, address, phone and tax ID print on every receipt (merchantAddress, merchantPhone, merchantTaxId, footer on the receipt payload).
  • Staff: add, edit name or role, switch off/on (ends their sessions immediately), reset password (ends their sessions). Safeguards: you cannot change your own role or switch yourself off, and the shop always keeps one active owner. PUT /v1/organizations/{id}/users/{userId}, POST .../password.
  • Branches, Devices (read only), Branding (white-label and domains; only where the plan allows).

Getting the catalog in#

  • Add product wizard (Details → Pricing → Picture → Review) for one at a time.
  • Import wizard for many: choose a CSV, match your own column headings (auto-matched where it can), preview what will be added, updated or skipped with a reason per row, then import. POST /v1/merchants/{id}/products/import with { csv, dryRun }. Columns: name, sku, price (naira, ₦1,250.50 is fine), optional cost, barcode, category (created if new), unit, tax, variant, favourite. Rows with the same product name and new SKUs become variants of one product. An existing SKU is updated, never duplicated, so fixing the file and importing again is safe. Bad rows are skipped and reported; good rows still go in.

Stock#

  • On hand, Receive, Adjust (as before).
  • Transfers: send stock between branches (Route → Items with on-hand hints → Review); the other branch confirms what arrived and shortfalls are recorded; cancel while in transit.
  • Counts: a stock-take sheet built for a phone and a desk.
    • Each item shows three things side by side: what the system says, what you counted (a big number box with − and + buttons, auto-saved), and the difference. A difference is always an icon plus a word (Short 2, Extra 3, Matches, Not counted), never colour alone, and the row gets a coloured edge. "Matches system" confirms an item in one tap.
    • Find things fast: a scan-or-search box (Enter jumps to the item; turn on Scan adds 1 and each scan counts one), and filter chips with live counts: All, To count, Matches, Differences. A running line shows Short, Extra and the net.
    • Blind count hides the system figure and differences while counting, so nobody counts to a number.
    • Review before posting: four cards (counted, short, extra, net, each with its value at cost), items grouped into Short and Extra with system → counted and the value, and a note listing how many were not counted (they stay as they are, with a shortcut to count them). Posting asks for a confirmation that says how many items will change.
    • A posted or cancelled count opens straight on its results. GET /v1/merchants/{id}/inventory/counts lists them; deep link /stock?tab=counts.