Point of Sale built for the real world

India's tier-2 and tier-3 retail reality is intermittent connectivity. A power cut takes out the router; the 4G tower three streets away drops to 2G during peak hours; a basement shop has zero signal. Every other cloud POS becomes a brick. X3 POS stays fully operational.

The local journal stores every cart action, payment, inventory decrement, and loyalty event with a monotonic sequence number and device clock timestamp. When offline, the POS commits transactions against an in-device inventory snapshot that was last synced. Inventory is tracked optimistically — if you sold 3 units offline and the central server shows 4 in stock, the merge reconciles to 1 on reconnect, with an automatic low-stock alert if the result crosses threshold.

Card payments work offline via offline card auth tokens pre-loaded through Razorpay and HDFC's offline auth protocol. UPI works through NPCI's UPI Lite offline mode for amounts up to ₹500. Cash transactions are always local. On reconnect, the replay engine pushes the journal in under 90 seconds for a typical 8-hour trading day (up to 500 transactions), with a real-time progress bar for the store manager.

Cart continuity is the gap every multi-channel retailer struggles with. X3 solves it end-to-end. When a customer builds a cart online, it gets a 6-character alphanumeric short code and a QR code. The customer shows either at the POS counter. The cashier scans or types it in. The full cart loads — line items, variant selections, bundle discounts, shipping fees converted to in-store pickup savings, promo codes, gift cards, and loyalty points earmarked for redemption.

The transfer is instantaneous because the cart lives in the shared edge KV layer (Cloudflare KV with consistent read mode) that both the storefront and POS read from. There's no "sync" — they're reading the same canonical object. The POS can modify the cart (remove an item the customer changed their mind about, add an impulse purchase), and those changes persist back to the cart if the customer wants to complete a different portion online later.

Ship-from-store is first class: any line item in a walk-in cart can be flagged for home delivery from the current store's stock, triggering a packing slip and courier pickup request without involving a separate OMS workflow. Returns work at any counter regardless of which channel the original order came from — the system looks up the order by phone, order ID, or QR on the receipt and applies the return against the original payment method with correct GST reversal.

Most cloud POS vendors either sell their own proprietary hardware at a margin or support a tiny certified list. X3 is hardware-agnostic within a well-tested reference stack, so you can use what you already own or choose the most cost-effective option for your market.

Payment terminals: BBPOS WisePad 3 (Stripe), Verifone P400, and Pine Labs A920 are the primary certified terminals covering Visa/Mastercard/Rupay tap, insert, swipe, UPI QR, and wallet tap. Terminal pairing is done via QR from the POS screen — no IP configuration, no manual serial entry.

Receipt printers: Star Micronics TSP143 and Epson TM-T82 are the primary receipt printer targets. Both support ESC/POS over USB and Bluetooth. GST-compliant receipts include GSTIN, HSN codes, tax breakdowns per line item, and a machine-readable QR that links to the digital receipt.

Kitchen Display System: orders flagged for KDS routing appear on Elo Touch or any Android tablet running the X3 KDS companion app. Routing rules are configurable per product category — burgers to Grill station, beverages to Bar station. Bump removes the item from the queue and fires a "ready" notification to the POS.

Barcode scanners: any USB HID or Bluetooth HID scanner works via the browser's keyboard event layer — no driver install, no configuration. Label printers (Zebra ZD220, Godex RT700) are supported for stock-room label printing direct from POS inventory view.

Cash drawers connect via the receipt printer's kick port (standard RJ-11) and open automatically on cash tender or manually via manager PIN. End-of-day drawer count is entered directly in POS, compared against expected (opening float + cash sales - cash payouts), and the variance is logged.

Store managers in growing retail chains typically find out about underperforming staff weeks late, through aggregated reports that obscure the individual signal. X3 pushes per-staff metrics live so coaching happens in the moment, not at the quarterly review.

The metrics engine runs on the server and pushes updates via WebSocket to any open manager dashboard. Latency from transaction commit to dashboard update is under 800ms. The key metrics tracked: units per transaction (UPT) against the store's configured target, attach rate (what fraction of transactions included a cross-sell or accessory), gross margin per transaction (not just revenue), refund count and refund value separated from void count (voids are pre-payment cancels, refunds are post-payment returns — very different operationally), and average transaction time from first item scan to payment complete.

Leaderboards are opt-in per location — some operators prefer individual coaching conversations over public rankings. When enabled, the leaderboard shows on the manager's display and on the staff-facing welcome screen at shift start. Shift performance is snapshotted at clock-out, so historical shift data is queryable ("how did Priya perform on Saturday evenings over the last 4 weeks?").

Upsell coaching is built in: the system can display a prompt to the cashier when a cart qualifies for a common attach ("customers who bought this lens also added a UV filter 68% of the time"). The prompt is configurable per category and can be suppressed for trained staff who find it distracting.

The failure mode of every bolted-on loyalty integration is the disconnect: the POS runs a simplified version of the loyalty rules, the online store runs the full engine, and customers inevitably exploit the gap or get frustrated by inconsistencies ("I earned 200 points online but the store says I only have 180").

X3 has no such gap. The loyalty engine runs server-side. When a POS transaction commits, it calls the same loyalty service that the storefront calls — same tier evaluation logic, same reward stacking rules, same multiplier events. The only difference is the input channel, which is recorded for analytics.

Customer lookup at the counter supports three modes: phone number typed in, email address typed in, or Apple/Google Wallet pass scanned from the customer's phone. The wallet pass shows the current points balance and tier badge and is updated in real time after each transaction. Points are awarded synchronously — they appear on the printed receipt and on the customer's pass before they leave the counter. No "your points will appear within 24 hours."

Tier notifications are delivered immediately: if the transaction pushes the customer over a tier threshold, the receipt prints "Welcome to Gold — you now have 2x on every purchase" and a push notification fires to their app within 10 seconds. Reward redemption at the counter shows a preview of the discount before confirmation so the customer can choose how many points to apply.

Access control in a multi-location retail chain needs two levels: what roles exist across the org, and what permissions each location assigns to those roles. X3 separates these cleanly. The organization defines roles (Owner, District Manager, Store Manager, Senior Cashier, Cashier, Trainee). Each location maps those roles to a permission set. A District Manager visiting a store they don't manage can view reports but not process refunds; the same person at their own store can.

Threshold gates prevent abuse without blocking legitimate operations. Refund limits: a Cashier can process refunds up to ₹500 without manager approval; ₹500–₹2,000 requires a manager PIN; above ₹2,000 requires manager NFC tap (the manager holds the NFC card near the terminal). Discount limits work the same way: a cashier can apply up to 10% manually; above that needs override. Price override limits are configurable per SKU category.

Manager override is tracked with the manager's identity — the audit log shows "Refund ₹3,400 on order #4521 by Cashier Deepa, approved by Manager Ramesh (NFC, 14:32:07)". This creates an unambiguous chain for loss prevention investigation.

End-of-day reconciliation is guided: the cashier counts the drawer denomination by denomination (the POS prompts for ₹2000, ₹500, ₹200, ₹100, coins), enters the total, and the system compares against expected. Variance above the configured tolerance (default ₹50) locks the till and notifies the store manager and district manager. The reconciliation report exports as PDF for the accounting team and feeds into the P&L dashboard automatically.