01
Choose a system of record for each shared fact
Write down which system owns product identity, descriptions, images, selling prices, tax configuration and available stock. Two teams editing the same price in different systems create reconciliation work even when data transfers are fast.
In Tellency’s storefront architecture, the catalogue, prices and stock come from the client’s ERP. The team controls online product and category publication there. This reduces duplicate catalogue maintenance, but it still requires good product data and a clear publishing process.
02
Map the order lifecycle, not just order creation
Define what happens after checkout: who accepts the order, which branch packs it, how delivery or pickup is selected and what marks it complete. A successful checkout response is only the start of the operational workflow.
Tellency’s online order flow includes new, accepted, packed, delivery or pickup and completed states. Completion records the configured sales invoice, payment and stock movement. Validate the branch and financial result using a representative transaction rather than assuming a status label proves the entire process.
03
Set the stock and price rules at checkout
Catalogue pages may be viewed before a price or availability changes. Decide what the customer sees when the cart is checked again and what staff do if goods cannot be supplied.
The checkout should validate the authoritative price and product state on the server. Test an out-of-stock item, a changed price, duplicate submission, an interrupted connection and a product that has been removed from online sale. Document the expected response for each case.
04
Test payment and cancellation exceptions
Distinguish selecting a payment method from collecting and settling the payment. Cash on delivery, card on delivery and bank transfer have different confirmation steps. An online gateway introduces authorisation, capture, settlement, refund and dispute events that need their own mapping.
Use a cancellation before fulfilment and a correction after invoice posting in the acceptance pack. Agree who may perform each action and what records should remain visible to operations and finance. Avoid using an order status update as a substitute for the required financial correction.
05
Turn the integration map into acceptance evidence
Assign an owner to every handoff. For each sample order, capture the original customer request, accepted quantities, packing branch, customer status, final invoice, payment record and stock change.
Run the same scenarios through the website and, if included, the iOS and Android apps. The channels should follow the same business rules even when the presentation differs. Repeat the checks after changes to products, delivery rules or payment configuration.
- One normal delivery order and one pickup order.
- A price or stock change between browsing and checkout.
- A repeated submit or connectivity failure.
- A cancellation and the approved financial correction path.
- Reconciliation of invoice, payment and stock results.
Questions to take into planning
What does ecommerce ERP integration connect?
It connects catalogue, pricing, inventory and customer orders to fulfilment and financial records. The exact responsibilities and transfer rules should be defined for the implementation.
Does Tellency require a second product catalogue?
Tellency’s own storefront reads the client’s ERP catalogue, prices and stock. Online publication is controlled through product and category settings.