Find the compliance gap before the purchase order, not after the container lands.
Your buyer raises a purchase order in your ERP knowing nothing about whether that supplier's paperwork is current. The gap surfaces weeks later — at goods-in, at an audit, or not at all. Connect DOSSA and your ERP can ask the question at the moment it matters: may I buy from this supplier, for this product, today?
Request accessDetection becomes prevention.
Every compliance system tells you afterwards. That is the whole category: a dashboard that goes red once something has already lapsed, reviewed by someone who is not the person spending the money. The buyer raising the order never sees it. Move the answer into the ERP and the order simply does not go out — no policing, no meeting, no chase. The check happens where the commitment is made.
- Your ERP can hold or flag a purchase order against a supplier whose paperwork is not current
- Per supplier, and per product — because a supplier covered for one thing is not covered for everything
- The reason travels with the verdict, so a buyer sees what is missing rather than just a block
- What is lapsing soon comes through too, so it can be chased before it becomes a block
Order lines tell DOSSA who you actually buy from.
Send the purchase lines you consider compliance-relevant and DOSSA compares what you bought against the suppliers and products it knows about. This answers a question a document system cannot: am I buying anything that nothing covers? A supplier verified for one product who quietly starts shipping another looks perfectly compliant until somebody notices.
- Nothing an ERP sends becomes a supplier or a product until a person says what it is
- Names that do not match are proposed, never merged on a guess — "A & P FRUIT GROWERS INC" is offered as A&P Fruit Growers, for you to confirm
- You choose the granularity: item and origin where the obligation follows the origin, item alone where it does not
- Cancelled orders stop asking to be mapped
Your ERP reads the verdict. On your schedule.
A read-only key, a documented API, and a job you run alongside the exporter you already have. It returns a status per supplier and per supplier-product, the reason behind anything blocked, what lapses inside a window you choose, and — the one nobody else publishes — how much of your vendor list DOSSA can answer for at all.
- One call returns every verdict; no looping, no rate-limit games
- A separate read-only credential: it cannot write, and your order-feed key cannot read compliance
- Either direction can be withdrawn without touching the other
- A coverage figure tells you how many of your vendors are not yet mapped — so you never switch on blocking believing it covers everyone
We never connect to your system. That is the design, not a gap.
Other vendors sell a connector, which means handing them write access to your vendor master. We publish a contract instead. Your systems talk to us, with credentials you hold and can revoke, and nothing we do can alter a record in your ERP. Someone on your side — or your ERP partner — writes the job, using a specification written so that an AI coding assistant can generate it from the document alone. Most of our customers' integrations are one scheduled task doing both directions.
- We hold no credential to your ERP and never write to it
- You write the job; we publish the contract and support whoever builds it
- No certified-connector claims and no vendor logos — every ERP is different and we would rather say so
- Works with any system that can make an HTTPS request on a schedule
Frequently asked questions
Do you have a connector for SAP, NetSuite, Odoo or Dynamics?
No, and deliberately. A connector means we hold write credentials to your system of record and maintain a field mapping into your vendor master. We publish a documented API in both directions instead, and your team or your ERP partner writes a scheduled job against it. You keep your credentials, we never write to your data, and the integration works with any system that can make an HTTPS request.
How much work is it to build?
One scheduled job doing two things: post the order lines from a trailing window, then read the compliance verdicts back. The specification is written so an AI coding assistant can generate a working integration from that document alone — which is exactly how our first one was built.
Will DOSSA create suppliers or products from our ERP data?
Never on its own. Everything the feed sends is proposed, and a person decides what it is — match an existing supplier, create a new one, or ignore it. An org that typed in forty suppliers by hand would otherwise end up with eighty, spelled two ways, each owing its own copy of the same documents.
Can DOSSA actually block a purchase order?
Your ERP blocks it; DOSSA supplies the fact it blocks on. We state whether a supplier and product are covered and why — your ERP applies your policy, which might be a hard hold, an approval step, or just a warning on the screen. Where the enforcement lives should be your decision, not ours.
What happens to suppliers our ERP sends that nobody has mapped?
They are reported as unknown, never as compliant, and we publish the count. That number is the most important one on the integration: without it a customer can switch on purchase-order blocking believing every order is checked while a third of their vendor list was never in scope, and nothing on either side would say so.
Is this only for food importers?
No. The order-line feed and the compliance read work for any business whose obligations attach to suppliers and what they supply. US food importers get FSVP verdicts in the same response; everyone else never sees them.
See if DOSSA is a fit.
Tell us about your operation and we'll show you exactly how DOSSA fits in.
No commitment. Reply within one business day.