Readiness
NetSuite already knows when the next delivery lands.
If you run NetSuite, the answer a buying agent most often cannot get anywhere is already sitting in your account: vendor lead time per location, expected receipt dates on open purchase orders, and the receipts that closed the last ones.
What stops most integrations is not the query. It is picking an authentication flow that does not quietly expire and send somebody back to a login screen.
Is NetSuite ready for agentic commerce and supply chain automation?
Ready for both, and it is the rare case where that comes easily. Every other system holding resupply data this good makes you work for access. NetSuite does not: machine-to-machine credentials, no recurring human consent, and lead time already in the schema.
One caveat. The richest lead-time fields sit behind optional paid modules, so on plenty of accounts lead time is a single global field on the item, or empty. Anything reading it has to check which case it is in rather than assume the best one.
Pick the auth flow that does not expire
The authorization-code flow issues a refresh token that defaults to two days and can be configured up to thirty, and it is single use. When it lapses you are sent back to the first step, which means a human sits down and re-consents. For a catalog an agent queries continuously, that is not a hiccup, it is an outage nobody notices until an order fails.
The client credentials flow has no user interaction at all. A certificate-signed assertion maps to an entity and a role, and you mint a short-lived access token whenever you need one. That is the only flow worth building on here.
Two operational details that bite later: the setup is not copied between accounts, so production and each sandbox need their own, and a sandbox refresh wipes it.
Where lead time actually lives
Lead time is held per item and per location, which is what makes it useful: an agent asking about a warehouse gets that warehouse's answer rather than a company-wide average. Expected receipt dates come off open purchase orders, so a promise can be traced to a specific inbound rather than inferred.
Worth checking on your own account before assuming the good case. Several of the richest fields depend on optional inventory and demand-planning modules being licensed. Without them the data thins to a single global field on the item, which is still better than most platforms manage and well short of what NetSuite can do.
An agent can place a real order on net terms
This is the part card-rail platforms cannot express. With machine-to-machine auth there is no human in the flow, the order is a real transaction rather than a cart, and payment terms come from the customer record, so it lands on net terms with no payment instrument attached at all. That is how B2B actually buys.
No webhooks, and it matters less than you would think
There is no native push. A delta poll on the last-changed timestamp every sixty seconds reads near-real-time to an agent and needs no code inside the merchant account, which is a fair trade. The real ceiling is account concurrency: integration slots are shared with whatever else the merchant already runs, so budget one or two and back off rather than assuming the account is yours.
Frequently asked questions
- Do I have to change my ERP?
- No. Connector reads the stack you already run. You do not migrate.
- Which systems does Conduit Connector support?
- WooCommerce and Odoo are in development. Shopify, Microsoft Dynamics 365, NetSuite, Salesforce Commerce Cloud, Oracle Fusion, SAP S/4HANA, and custom API or MCP are coming soon. Per-stack notes live in Hub.
- What happens after the graph is in Hub?
- Pipes run standing jobs on that map: a disruption brief before coffee, plus restock, price, and parcels.