From Closed Won in Salesforce to a checked sales order in your ERP

Salesforce tells you what sales has agreed. Your ERP decides what gets picked, shipped and invoiced. In plenty of UK distributors, the bridge between the two is a person reading an opportunity or quote and retyping it, often days later and occasionally with the wrong price.

Zestcode Automation builds a bespoke platform that takes won opportunities, quotes and rep-entered orders from Salesforce, checks them against your ERP for stock, price and customer details, and creates the sales order once someone in operations approves it. It also reads customers’ emailed POs and links each one back to the matching Salesforce account.

Three ways an order starts, one queue

Orders in a Salesforce-led business usually begin in one of three places:

• A won opportunity or accepted quote. The products, quantities and agreed prices are already in Salesforce. The work is checking they still make sense to the warehouse.
• An order a rep enters in Salesforce, perhaps on a customer visit, without sight of current stock.
• A purchase order the customer emails after agreeing the deal, which may not quite match what was quoted.

All three end up in the same review queue, so operations has one place to look. Emailed POs are read by AI from the email body and attachments, with a confidence score out of 10 on every field and anything under 7 flagged. Orders from Salesforce don’t need reading, but they go through exactly the same checks.

Can the ERP actually fulfil what was sold in Salesforce?

Answering that before anything is created is what the platform is for. For each line, code compares the Salesforce data or the emailed PO with your ERP:

The last check matters more than it sounds. When a customer emails a PO for a deal already closed in Salesforce, two orders for the same goods are an easy mistake. The platform spots the overlap and puts both in front of the reviewer instead of letting them through.

Linking emailed POs back to Salesforce

Sales teams like seeing what happened after the handshake. When an emailed PO arrives, the platform matches the sender to an account and, where you want it, to the open or recently won opportunity. Once the order is approved and created in the ERP, a reference such as the ERP order number or its status can be written back to Salesforce so the account owner can see it without asking the office. Exactly which records and fields are updated is agreed in the specification.

After approval: ERP, warehouse, carrier

Approving creates the sales order in your ERP the way your staff would, with the customer’s PO number as reference. The ERP remains the system of record for stock and invoicing. If you add the later stages, the order then appears on warehouse devices for picking and packing, and the shipping stage prices and books the carrier, prints the label and saves the tracking. A delivery charge that doesn’t match what the customer’s PO allowed for is held for the office to decide.

What we need from your Salesforce org

The platform connects through Salesforce’s API. Whether API access is included depends on your Salesforce edition and add-ons, so we check that early. We also look at how you use opportunities, quotes and orders today, whether you have CPQ or custom objects, and who in your team owns the Salesforce setup. Your sales process doesn’t have to change; the platform reads from it.

Ownership and pricing

When it’s live, the platform is yours. It runs on hosting set up in your company’s name, carries no per-seat fees on top of what you already pay Salesforce, and support afterwards is optional.

Indicatively, the order automation stages cost £8k–£12k ex VAT over about six weeks. Adding warehouse and shipping takes it to £20k–£30k across two phases and roughly 14 weeks in total. You’ll get a fixed quote, valid for 90 days, after a free written specification.