“The first version of the Orders module does not connect to accounting, ERP, inventory or delivery systems. Exports cover that gap until a connection has been built and proven end to end. We publish no list of systems we connect to and no logos.”
6 things.
And what each one is for.
Take all of it out, any time
Filter a set of records on screen, choose CSV, XLSX, XML or TSV, and take it. All four carry the same permitted records and the same fields, each with a documented schema, so the file opens in whatever your accountant, your analyst or your next system expects. Order exports work the same way.
Benefit Leaving is a menu option, not a negotiation.
Proof: CSV · XLSX · XML · TSV · documented schema
Every export leaves a record
Who asked for it, which filters, which fields, how many rows, which format, when it was created and when it expires. The audit record does not contain the personal data itself. Cell content beginning with an equals, plus, minus or at sign is neutralised so a spreadsheet does not run it, while the value stays readable.
Benefit If somebody walks out with a customer list, that is a question with an answer.
Proof: Requester · filters · row count · expiry · formula neutralisation
Orders and Customers are one system
Orders uses the same customer records as Customers, so there is nothing to sync between them. Orders show on the customer's record and feed its order value, and an order can be linked to a deal. This arrives with the Orders module, which is taking pilot customers.
Benefit No second customer list to keep in step with the first.
Proof: Shared customers · order history on the account · order linked to deal
Inbound capture contracts
A versioned REST API reads your customer list and accepts a new lead from another system: a title, its source and a stage, without contact details. Signed webhooks accept lead and activity events. Both check the schema and are idempotent, so a retried delivery does not create a second lead. Connecting your website to it is developer work.
Benefit A new source can send data in without writing directly into the database.
Proof: REST API · signed webhook · schema validation · idempotency
Honest connection states
A connection is described by where it actually is: planned, contract verified, sandbox verified, or live. Nothing is called live before credentials, sandbox verification and an end to end receipt exist. That is a written product rule, which is why this page has no logo wall.
Benefit You are never told a connection is ready on the strength of somebody having drawn it on a diagram.
Proof: Planned · contract verified · sandbox verified · live
Imports during setup
We load your customers, products and price lists with you during setup, from a spreadsheet or an old system, so you begin with real records instead of an empty screen. Products and prices go through the import preview in the product.
Benefit Data scattered across spreadsheets is the work, not an obstacle.
Proof: Products and prices: import preview · Customers: loaded during setup
Four steps, in this order, every time.
- 01
Export
Take any filtered set of records in four formats.
- 02
Record
Every export is logged, without the data itself.
- 03
Scope
Name the system, the fields and the direction first.
- 04
Prove
Nothing is called live without an end to end receipt.
Thirty minutes, and you leave with three answers.
Whether a pilot fits the way your orders arrive, what we would set up, and what it would cost. Written down, so you can put it in front of a partner or a board.
Bring three things
- A few real orders, as they arrive today.
- Your product and price list, in whatever form it is in.
- Who takes and confirms orders now.
Leave with three answers
- Whether the pilot fits.
- What we would set up, and how.
- What it would cost, written down.