SalesDrive is used to organise sales workflows from an initial request through dispatch and payment. A store needs visibility into products, delivery, documents and the final outcome, not just customer contact details. A sound implementation starts by agreeing this journey between managers, the warehouse and accounting staff.
An order should retain its purchase context
Send agreed fields from the website: order number, products, quantities, prices, contacts and delivery method. Each product needs a stable code. Even if website and CRM names differ, the manager should receive the correct item. Sending arbitrary text instead of an agreed identifier complicates stock management.
The official SalesDrive reference describes APIs for orders, products, payments and reference data, as well as webhook notifications. Check a proposed integration against those capabilities and your environment. Ready-made connectors need testing too, because they may not transfer every field the business requires.
Keep sales, delivery and payment states distinct
An order may be confirmed and a shipment created while payment is still outstanding. A single completed label does not explain these differences. Agree which events mean dispatch, delivery and payment confirmation. For cash on delivery, separately identify the source confirming actual receipt of funds and who reconciles differences.
-
A created waybill does not yet mean the parcel was handed to the carrier.
-
Parcel delivery and final payment settlement may happen at different times.
-
Product returns and refunds are related but separate events to verify.
Learning example: a customer did not collect a parcel
A store dispatches an item, but the customer refuses delivery. Changing one CRM status is insufficient. Define when the item returns to available stock, how shipping costs are recorded and what happens to the expected payment. Before the warehouse physically accepts the return, the item may still be in transit rather than ready for resale.
Follow the complete cycle with a test order and reconcile entries in the connected accounting system. This reveals which actions are automatic and which need employee confirmation. The test aims for an agreed outcome, not the maximum number of automatic status changes.
How we prepare a store’s SalesDrive integration
For an ALL IT Agency implementation task, we define a field map and status correspondence table. Before development, we check product, delivery address, discount and payment formats. An external order number helps recognise repeat submissions. Access keys belong in the server-side integration, not in the buyer’s publicly accessible page code.
What the team should be able to do after launch
Managers should be able to find an order by its website number, explain its state and identify the next action. The integration owner needs visibility into failed exchanges and a recovery procedure. A pilot covers a normal sale, repeated submission, item changes and a return. Confirm plan and external-service capabilities before agreeing the final scope.
Sources and further reading
