services / DSDillon
Custom POS Software Development
Build a checkout around your products, prices, customers and daily close. Connect the counter to invoices, stock movements and the accounts.
Start with a real trading day
A customer changes a quantity, asks for a discount and needs an invoice. Another leaves a deposit and collects the goods tomorrow. These events determine the screens and records your POS needs. We work through them with your team before choosing the checkout layout.
The specification covers product search, barcode input, variants, units of sale, held orders, returns, customer accounts and payment states. Each action has an expected result in the stock record and financial ledger. Owner approvals sit beside the actions that need them.
Test the equipment at your counter
Bring the model numbers for your tablets, terminals, scanners, cash drawers and printers. We agree supported operating systems and connection methods, then test the exact combination. Receipt width, long product names, repeated scans and a failed print job belong in that test.
Offline operation needs durable local sales, device authorization, receipts, a recovery queue and a procedure for two registers selling the same item. Card authorization depends on the payment provider and reader.
Give every sale a traceable history
A completed sale needs one transaction identity. Retrying a request after a lost connection should return the existing result. A return identifies the original item, customer credit and condition of the goods.
| Workflow | Acceptance check |
|---|---|
| Counter sale | One receipt, one payment allocation and one stock deduction |
| Held order | Resume the basket with its customer and currency |
| Return | Link the credit, confirmed refund and stock condition |
| Daily close | Reconcile each currency and payment method |
Agree the launch and support arrangements
Delivery includes the approved workflow, data structure, operator guidance and acceptance results for the agreed scope. Hosting, source code rights, third party licences and maintenance are recorded in the contract.
We rehearse a trading day using sample records, reconcile opening stock and approve the launch window. Historic records remain available under the agreed retention arrangements.
Before you start
Can you build a POS for several branches?
Yes. The scope can include branch stock, local registers, shared catalogue rules, permissions and central reporting. Separate legal entities need intercompany rules.
Can we use our current payment terminal?
We check its model, provider, operating country and integration options. An integrated terminal needs a tested connection.
Build the complete workflow
Related services
POS and Accounting Integration Services
POS accounting integration for sales, taxes, refunds, stock and settlements. Custom mapping, duplicate protection, monitoring and reconciliation.
Explore the service servicesInventory and Purchasing Software Development
Inventory software development for purchasing, transfers, counts, batches, serials and landed costs, connected to POS and accounting.
Explore the service deliveryPOS and Accounting Project Delivery
From workflow review and prototypes to migration, acceptance tests, launch and support. See how a DSDillon software project is delivered.
Explore the serviceYour next system
Tell us what needs to work.
Bring your trading workflow, current software and the problems you need to solve. We will define the build, connections and acceptance checks.
DSDillon Business Systems
POS, accounting and connected operations.
