What is available, what is in beta, what is planned.
One table, kept current, last checked September 23, 2026. Generally available means on the plans named with no switch to ask for. In beta means built and working, turned on per account by us. Planned means not in the product today.
| Capability | Status | Plan or condition |
|---|---|---|
| Purchase-order reading from PDF, spreadsheet, scan, photo, email body, Word and text files | Generally available | On every plan. Unsupported file types are refused at intake with a reason. |
| Supplier-invoice reading and review | Generally available | On every plan. Every invoice is reviewed by a person; there is no automatic approval for invoices. |
| Email intake: shared inbox, your own IMAP mailbox, Gmail, Microsoft 365 | Generally available | Gmail and Microsoft 365 connect with OAuth. Until our provider redirect addresses move to the web origin, a mailbox connect can fail with a "finish in the same browser" message; email support if you see it twice. |
| SFTP, manual upload and API intake | Generally available | On every plan. |
| Human review queue with the source document, per-field confidence and validation findings | Generally available | On every plan. |
| Auto-approval on your confidence thresholds, with the ramp-up that lowers the bar as clean approvals accumulate | Generally available | Off by default. You turn it on; every later check can only add review. |
| Shadow line on the Trust page: what would have run unattended on your settings | Generally available | Measured per week for the whole account from day one. |
| Shopify draft orders | Generally available | OAuth connect on every plan. |
| NetSuite sales orders | Generally available | Guided token-based setup; accepted against your own account during onboarding. |
| Your own REST endpoint (signed, with idempotency keys) | Generally available | On every plan. |
| CSV and EDI 850 file export | Generally available | On every plan, and the fallback when no connector is configured. |
| Routing to one of several connected stores | Generally available | Growth and above, with per-plan limits on stores and rules. |
| Supplier-invoice write-back as a QuickBooks Bill or NetSuite vendor bill | Generally available | Requires a default expense account on the connector. |
| Buyer order acknowledgements | Generally available | Emailed to the buyer and delivered as a webhook event. |
| REST API, OpenAPI spec, MCP server (186 tools), signed webhooks | Generally available | On every plan. See the developers page. |
| Append-only audit log with nightly export to object storage | Generally available | Object Lock on the export bucket is monitored but not yet confirmed in production. |
| Full-tenant export, retention purge, offboarding | Generally available | From Settings and the API. |
| Per-customer autonomy: grant, revoke, sender verification, anomaly holds, instant demotion | In beta | Built and off by default. Beta programme; ask us. |
| QuickBooks Online Estimates or Invoices | In beta | Connector complete; self-serve connection waits on Intuit production verification. Ask sales for the current date. |
| Writing one order to a store and to your books at once | In beta | Growth or Scale add-on. Ask us to enable it. |
| SAML and OIDC single sign-on with enforced-SSO domains | In beta | Built; live acceptance against a customer identity provider is outstanding. Enterprise plan. |
| Shared buyer layouts across customers (Format Library) | Planned | Built and switched off everywhere until the data-processing terms are settled. |
| SAP Business One, Dynamics 365 and Odoo connectors | Planned | File export today. |
| Inbound EDI 850, outbound 855 and 856 | Planned | Outbound 850 export only today. |
| SOC 2 report, contractual uptime, recovery objectives, EU residency | Planned | Not offered today. See the security page for what is. |
How to read this page
A capability is listed as generally available only when it runs for every account on the plans named, with nothing for us to switch on. Beta capabilities are complete in the product but enabled per account, because the evidence that they behave under real traffic is still being collected; ask and we will tell you what that evidence looks like today. Nothing on this page is a commitment to a date. A capability moves from planned to beta when it is built, and from beta to available when it has run for beta accounts without surprises.
Questions about this table
What does "beta" mean here?
Built and working in the product, turned on per account by us rather than a self-serve switch. We can tell you exactly what evidence we are still collecting before it moves to generally available.
Can I get an available date for something planned?
No. A capability moves from planned to beta when it is built, not on a promised date, so nothing on this page is a commitment to a date.
Who keeps this table accurate?
Every row is checked against the same evidence our own engineering ledger uses, and the date at the top of the page moves only when a row changes, not on every deploy.