An online store is more than product pages and a payment button. After a customer places an order, pricing, stock, the payment provider, warehouse and delivery must work together. If they are disconnected, a customer may pay for an unavailable item while the manager learns about the order only from a stray email. Understanding the full journey helps before choosing a platform.
The catalogue defines the selling rules
First define what is being sold: a product, a size and colour variation, a bundle or a service. Each separately stocked item needs a consistent identifier. Its customer-facing name may change, but the accounting system must recognise the same item. Pricing, tax, discount, availability and measurement-unit rules also need to be defined.
A product page should explain specifications, included items, delivery and return terms. Filters should reflect the characteristics people actually use to choose. For a cable, length and connector type are more useful than a supplier’s internal category name.
An order and a payment are different events
An order may already exist while its payment is still awaiting confirmation. A customer returning to the thank-you page does not replace server-side payment verification. The payment provider sends a separate event; its authenticity must be checked, and repeated delivery must not cause another stock deduction or create another document.
In a learning scenario, a customer places an order, closes the tab during payment and receives bank confirmation later. The store should update the status correctly without an open browser tab. If the same payment notification arrives again, the order outcome should remain unchanged.
Where the authoritative stock balance lives
Before development, agree which system manages stock and reservations. A small store may use its own platform; a company with offline sales may use accounting software or a WMS. Define when stock is reserved, how long payment may be awaited and what happens on cancellation. Otherwise, the same last item may be promised to different customers.
-
Test simultaneous orders for the same item.
-
Agree what happens when the accounting system is unavailable.
-
Account for partial dispatch, cancellation and product returns.
How we approach a store’s integrations
The ALL IT Agency service page treats a store together with its catalogue, payments, CRM and accounting. A useful specification records not just the connected services but the actual events: order created, funds confirmed, stock reserved and shipment booked. Each event needs a responsible system and a way to verify the result.
The practical output is an exchange diagram, a status table and a list of failure situations to test. These give accounting staff, warehouse workers and developers a shared understanding of what a paid or cancelled order means.
What to test before acceptance
Complete a mobile purchase without an account, with a failed payment and with a retry. Reconcile delivery charges, discounts, customer notifications and accounting entries. Then test refunds and returned stock. Seeing a success screen is not enough: the manager must find the order, the warehouse must see the correct reservation, and the customer needs clear confirmation and a support contact.
Sources and further reading
