Follow the complete merchandise journey
Map receiving, internal labelling, transfers, reservations, sales and returns. Establish where payments are recorded and who may correct mistakes. When a warehouse, shop and courier share an order, each participant needs an explicit state and next action. Include partial deliveries and mismatched items, using anonymised documents.
Choose the necessary components
Scope can include checkout, a product catalogue, stock control, pricing and management views. A specialised workstation may need a Windows application; several stores may need a central service with local components. Existing accounting software need not be replaced. Separate the mandatory first release from later capabilities rather than commissioning an unnecessary universal platform.
Integration and equipment boundaries
Assign authoritative sources for prices, products, stock and payments. Verify APIs, access and retry rules. Scanners, scales, printers and terminals require checks against actual models, drivers and protocols. Fiscal exchange requires a selected local provider, contractual arrangements and the necessary access. Building an integration does not establish compliance with every applicable legal requirement.
Failures, access and data ownership
Define which tasks may continue offline and which require server or payment-provider confirmation. A locally stored sale is not a confirmed payment. Log operation identifiers and outcomes without secrets. Roles restrict discounts, cancellation and exports. Agree ownership of source code, database and infrastructure accounts.
Delivery and rollout
Document workflows, prototype the main workstation and build an agreed first scope. Test against selected equipment before a controlled pilot with named users, permitted data and a rollback plan. Hand over operating and backup instructions. Expand only after reconciling stock, reports and pilot findings.