Integrations · ERPNext
Count the warehouse, and ERPNext gets a stock reconciliation.
The approved count lands as a Stock Reconciliation — a document your accountant already reads.
What moves, and which way.
Down, before the count
Items and warehouse stock come down as the counting catalogue. Contact links are qualified by role, because ERPNext names a Customer and a Supplier identically and the two must not be confused.
Back, after you approve
The approved count lands as a Stock Reconciliation against the warehouse you chose, with the variance lines on it. Nothing is posted while the write flag is off.
Nothing is written until you approve it. The count sits on the hub, the variances are reviewed there, and the write is one pass at the end that you start.
Self-hosted means the hub connects straight to it.
What you supply
A self-hosted ERPNext, and an API key and secret you generate in it. Direct connection, no broker, no SoftBo server in the path.
One countone warehouse
Postingbehind a flag, off by default
Namingroles are qualified, not guessed
What it cannot do yet, before you buy rather than after.
- One count, one warehouse. A site with three warehouses runs three counts, and each lands as its own reconciliation.
- Posting is behind a flag that is off by default. Turning it on is a decision somebody takes once, on purpose, rather than a default that surprises a live system.
- Roles are qualified, not guessed. ERPNext names a Customer and a Supplier identically, so a contact link carries which one it is — a mismatch there is what used to block a document push.
- It has not been run against a live ERPNext. The code is written and tested against a stub, and the write path ships behind a flag that is off. The date below is empty on purpose, and it is the honest state of it.
[VERIFIED · DATE] and [SETUP TIME]. Both close the first time SoftBo writes to a real ERPNext. That one afternoon turns this page, the integrations page and CLAIMS C1–C3 green together.