Commerce & Payments · Integration
Neto
Add Neto to your product for your customers, and give your AI agents governed access to it.
Embed a Neto integration so your product can work inside the stores Australian and New Zealand retailers already run. Neto, now sold as Neto by Maropost, is a multichannel commerce platform that carries ecommerce, point of sale, inventory and order management together, so the objects your product touches are products, orders, customers, inventory levels and fulfilment records. Each merchant connects their own store with their own API credentials, so reads and writes are scoped to their tenant and every call is logged. Order and fulfilment writes are idempotent, which matters because a retry after a timeout must not duplicate an order somebody will ship. fastn owns the auth, retries, pagination and API upkeep, and the same connection serves your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each merchant connect their own Neto store so orders, products and customers appear inside your product with no per-customer code.
Write products and inventory levels into a merchant's store so your product is the source of truth for what is sellable.
React to a new or updated order so fulfilment, accounting or entitlement steps in your product run on the event rather than a nightly sync.
Read order and fulfilment history per tenant so support and reporting in your product reflect that merchant's own store.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers where a customer's order is by reading that merchant's own Neto records, with the read audited.
An agent updates stock or a product detail within scoped permissions, with the write attributed to the store that authorised it.
An agent summarises which products sold across a merchant's channels last week without anyone exporting a report.
Example prompt
Look up this Neto order, tell me its fulfilment status, and check whether the item is back in stock.
Set up Neto in 4 steps
- 01Enable the Neto connector in your fastn dashboard.
- 02Have each merchant supply API credentials for their own store so calls run under their access.
- 03Map the product, order, customer and inventory fields your product uses, per merchant.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Neto integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Neto integration without building it. Your customers connect their own Neto account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Neto update is not your on-call problem.
- One integration serves your product and your agents. The same governed Neto connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
BigCommerce
Magento 2Often used alongside
Tools the same teams tend to run next to Neto, across other categories.
NetSuite
Notion
Box
DocusignNeto integration FAQ
How do I add a Neto integration to my product?
Enable the Neto connector in your fastn dashboard, then let each customer authenticate their own Neto account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Neto client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Neto account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Neto account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Neto integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers where a customer's order is by reading that merchant's own Neto records, with the read audited.
Who maintains the Neto integration?
fastn does. When Neto changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Neto integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Neto integration?
A common starting point: let each merchant connect their own Neto store so orders, products and customers appear inside your product with no per-customer code. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Neto integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Neto does not change your per-connector cost. You can start free with 3 connected accounts.
Add Neto to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.