Products · Sales, Stock & Till

Sales, Stock & Till

The full point-of-sale layer on top of payments: a product catalog, barcode-driven stock control, sales settled by cash or InnBucks, and daily reports — plus a bundled Till app at /till that needs zero code. Everything the till does is also plain REST, so any custom frontend can do the same.

The model — three objects

Catalog

curl https://omniway.online/v1/products \
  -H "Authorization: Bearer sk_live_..." -H "Content-Type: application/json" \
  -d '{
    "name": "Bread 700g",
    "barcode": "6001234567890",
    "price_cents": 150,
    "track_stock": true,
    "stock_qty": 20,
    "low_stock_at": 5
  }'

• barcode is unique per merchant — the scanner contract. 409 barcode_taken on duplicates.
• price_cents: null = price decided at sale time (hardware off-cuts, taxi fares, consultations).
• track_stock: false for services — sellable, never counted.
• Soft-delete with PATCH {"active": false}; history stays intact.

Search/list: GET /v1/products?q=bread, exact scanner lookup: GET /v1/products?barcode=6001234567890.

Barcode scanners (and other capture)

USB and Bluetooth barcode scanners are keyboards — they type the code and press Enter. No drivers, no SDK:

scanBox.addEventListener("keydown", async (e) => {
  if (e.key !== "Enter") return;
  const code = scanBox.value.trim(); scanBox.value = "";
  const { data } = await till.get(`/products?barcode=${encodeURIComponent(code)}`);
  data.length ? cart.add(data[0]) : showNoMatch(code);
});

The bundled Till app works exactly this way — keep its scan box focused and scan away: scan-to-sell on the Sell screen, scan-to-receive on the Stock screen. The same pattern accepts any keyboard-wedge input device (membrane keypads, QR wands, magstripe readers in keyboard mode).

Stock control

# goods in from a supplier
curl …/v1/stock/receive -d '{"product_id":"…","qty":24,"note":"Delivery — Lobels"}'

# damage/shrinkage correction (signed delta)
curl …/v1/stock/adjust -d '{"product_id":"…","qty":-2,"note":"damaged"}'

# stocktake: set the counted absolute quantity
curl …/v1/stock/count -d '{"product_id":"…","qty":18,"note":"monthly count"}'

Every change is a journal row (GET /v1/stock/moves) — who/when/why for any discrepancy. GET /v1/stock/report returns on-hand units, valuation at current prices, and the low-stock list (products at or below their low_stock_at).

Sales

curl https://omniway.online/v1/sales \
  -H "Authorization: Bearer sk_live_..." -H "Content-Type: application/json" \
  -H "Idempotency-Key: till3-0611-0142" \
  -d '{
    "tender": "cash",
    "items": [
      {"product_id": "…bread…", "qty": 2},
      {"name": "Delivery", "qty": 1, "unit_cents": 100}
    ],
    "cashier": "Rudo"
  }'
# → status:"completed" immediately; tracked stock decremented

Line items are {product_id, qty} (price from the catalog, overridable with unit_cents) or fully ad-hoc {name, qty, unit_cents}. Items snapshot name and price at sale time — later catalog edits never rewrite history.

curl … -d '{"tender": "innbucks", "items": [{"product_id": "…coke…", "qty": 2}]}'
# → status:"pending" + embedded payment { code, qr_png_data_url, deep_link, checkout_url }
# show the code/QR; the sale completes itself when the customer pays
# (poll GET /v1/sales/:id, or act on the sale.completed webhook)

If an InnBucks payment expires unpaid, the sale auto-cancels (status: "cancelled") — no stock moves, no money. Ring it up again for another attempt.

Reports

curl ".../v1/sales/report?from=2026-06-11T00:00:00Z" -H "Authorization: Bearer sk_live_..."
# → by_tender: cash vs innbucks count + totals per currency
#   top_products: best sellers by revenue
#   totals: overall count + per-currency takings

Pair with GET /v1/stock/report for the full picture: what sold, what it took, what's left and what it's worth. Money-side reporting (fees, payouts, statement CSV) stays on the ledger.

The bundled Till app

https://omniway.online/till — sign in with your dashboard credentials. Three screens, phone-and-tablet friendly, no installation:

The TEST/LIVE pill in the header switches worlds — train new staff in TEST, where sales are simulated and stock is untouched. The till speaks to the same API documented above; if it ever feels limiting, build your own frontend against /v1 and keep the data.

Industry presets — same engine, different habits