Included capability
This capability is part of the BPT core business suite and can be enabled when the organization setup, plan, and user roles are ready.
Included now
POS, Sales & Order Operations
POS / Trade
Counter billing, receipts, parked bills, returns, day close, order fulfillment, and shared return handoff.
How We Enable It
Confirm organization setup
Assign user access
Add required business data
Check the workflow with your team
Included Facilities
These are the facilities a buyer can understand before setup. The actual workspace shows only the menus and actions allowed for the organization, selected plan, and user role.
POS checkout
Enabled through BPT setup and shown to the right users when the organization is ready.
Returns
Enabled through BPT setup and shown to the right users when the organization is ready.
Day close
Enabled through BPT setup and shown to the right users when the organization is ready.
Order fulfillment
Enabled through BPT setup and shown to the right users when the organization is ready.
Commercial Pack Picture
What Can Be Sold From This Capability
These packs show the practical buyer-facing scope while keeping every business rule inside the owning BPT module and backend service.
Retail Counter POS
Sellable retail package for grocery, mart, apparel, cosmetics, gift, and everyday counter billing where the customer needs fast checkout with governed stock and payment impact.
Owner: POS with Catalog, Inventory, Payments, Tax, Posting, and Finance support
- Barcode or search-based checkout with receipt and reprint support
- Cash, card, UPI, split, credit, pending, and retry-safe payment recovery handling
- Returns, refunds, shift close, day close, tax snapshot, stock impact, and posting handoff
Grocery POS With Device Setup
Grocery package for weighted items and high-speed counters after the customer printer, scanner, scale, and cash-drawer path is verified.
Owner: POS plus Provider Management and Device Management
- Weighted item, unit, barcode, tax, and stock setup through owning modules
- Printer, scanner, weighing scale, and cash drawer readiness gate
- No automatic payment-status polling; operators use clear retry or recovery actions
Restaurant Settlement Bridge
Restaurant and KOT should be sold under Hospitality. POS participates only where counter-style settlement, receipt, or payment handoff is configured.
Owner: Hospitality owns restaurant, table, KOT, KDS, bar, folio, and pass flows
- Hospitality-owned table, waiter, menu, KOT, KDS, restaurant, and bar flow
- POS-style receipt, counter settlement, and payment handoff only where configured
- Void, refund, pass cancellation, tax, stock, and posting authority stays backend-owned
Electronics Serial And Warranty POS
Electronics package for stores that need serial, IMEI, accessory bundling, warranty, exchange, and controlled refund workflows.
Owner: Catalog, Inventory, POS, Warranty, Payments, Tax, Posting, and Finance
- Serial or IMEI capture tied to Catalog and Inventory source records
- Warranty and exchange notes with manager-authorized return and refund paths
- Payment, stock, tax, posting, and audit trail review after each sensitive action
Chain Store POS
Enterprise package for multi-branch retailers that need organization scope, branch counters, central controls, reporting, and role-wise visibility.
Owner: Platform, Catalog, Inventory, POS, Payments, Finance, and Reporting
- Branch and counter setup with role, subscription, and organization isolation
- Central product, price, stock, customer, payment, and generated-impact reporting
- Server-side paging, search, filters, and guarded direct-route/API access
Ownership Guardrails
Source Of Truth By Area
Product, barcode, price, tax defaults, and service catalog
CatalogUsers select products from approved lookups; POS must not create hidden product, tax, or price facts.
Stock balance, stock ledger, warehouse, transfer, and adjustment impact
InventorySale, return, and void outcomes must be verified against backend-owned stock and generated ledger records.
Counter billing, parked bills, receipts, return handoff, shift close, and day close
POS / TradeActions are visible only when role, status, subscription, organization, and business state allow them.
Restaurant, bar, table, KOT, KDS, service coupon, pass, folio, and booking flow
HospitalityRestaurant/KOT is not a generic POS promise; POS is only the configured settlement or receipt bridge.
Payment status, gateway retry, tax snapshot, posting queue, ledgers, and financial reports
Payments, Tax Charges, Posting Engine, and FinanceBackend services remain the authority for amount, tax, payment, posting, and accounting transitions.
Printers, scanners, weighing scales, payment terminals, SMS, WhatsApp, email, and delivery integrations
Provider ManagementNo provider id, device endpoint, credential, or behavior is hard-coded in POS pages or public catalog copy.
Operator Flow
How Daily Work Should Run
Retail Counter Flow
- 1Prepare products, units, barcodes, taxes, prices, and stock in Catalog and Inventory.
- 2Open the correct organization, branch, counter, and shift with role-approved access.
- 3Scan or search items, apply allowed discounts or loyalty, and collect the selected payment mode.
- 4Print or send the receipt, then review payment, tax, stock, posting, and day-close impact.
Payment Failure Recovery
- 1Show the backend payment state clearly when a gateway or terminal payment is pending or failed.
- 2Offer an operator retry, alternate payment, or manager-approved cancellation path without automatic status polling.
- 3Keep idempotency, reason, actor, organization, and audit evidence for every retry or recovery decision.
- 4Update the final payment, posting, stock, and receipt state only after backend confirmation.
Hospitality Settlement Handoff
- 1Create table, KOT, KDS, restaurant, bar, or folio actions inside Hospitality first.
- 2Use POS only for configured counter settlement, receipt, or payment handoff.
- 3Apply void, refund, pass cancellation, and reversal authority through backend-approved workflows.
- 4Verify payment, tax, stock, posting, and audit effects in the owning modules after settlement.
Production Readiness
Ready Scope And Boundaries
This keeps the public promise aligned with the backend-owned module rules, provider readiness, and rollout evidence needed before customer go-live.
Backend authority
Ready for governed rolloutPublic POS packaging keeps validation, authorization, organization scope, amounts, taxes, stock, posting, payment state, and audit under backend ownership.
Enterprise and normal-user fit
Ready for positioningRetail, grocery, electronics, restaurant bridge, and chain-store packs are visible with clear ownership so small shops and organizations can choose the right setup.
Payment retry behavior
Policy definedFailed or pending payments are positioned around explicit operator retry and recovery actions, not automatic payment-status polling.
Hardware and offline claims
Customer setup gatePrinters, scanners, scales, terminals, cash drawers, KDS devices, and offline billing are not marked universally live until provider/device replay passes.
Hospitality separation
AlignedRestaurant, table, KOT, KDS, folio, bar, pass, and booking flows are clearly kept under Hospitality ownership.
Do Not Over-Promise These Items
- Do not sell physical weighing scale, printer, scanner, cash drawer, KDS, payment terminal, or offline mode as live until the exact provider or device is configured and replayed.
- Do not let POS duplicate Catalog, Inventory, Payments, Tax, Posting, Finance, or Hospitality business rules.
- Do not expose branch, organization, role, customer, supplier, ledger, product, warehouse, or tax ids as manually typed public or operator-facing values.
- Do not claim Hostinger production completion until the selected artifact is deployed and replayed on the canonical public URLs.
Clear Product Positioning
This page keeps the public message simple: what this capability does, when it can be enabled, and which workspace the customer uses after setup.
Availability: Included nowCategory: Core Business SuiteScope basis: Product setup