--- title: "Neto Integration" description: "Neto, now sold as Maropost Commerce Cloud, is an Australian ecommerce, POS and inventory suite. Agents keep stock in step with warehouses and suppliers, hand new orders to a 3PL or accounting system, manage products, customers and vouchers, and quote shipping." url: https://flowrunner.ai/integrations/neto date_modified: 2026-09-04T19:08:45-07:00 --- # Neto [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Neto, now sold as Maropost Commerce Cloud, is an Australian ecommerce, POS and inventory suite. Agents keep stock in step with warehouses and suppliers, hand new orders to a 3PL or accounting system, manage products, customers and vouchers, and quote shipping. 42 actions · API key · available [Neto website](https://myshop.com.au/) · [Platform Documentation](https://developers.maropost.com/) · Capability data verified 2026-08-26 1. A scheduled poll calls Get Orders with the update window set to the last run 2. Agent reads each order's lines, SKUs, quantities and shipping method 3. Get Products confirms the ordered SKUs still hold stock in the warehouse the order ships from 4. Each clean order goes to the third-party logistics provider, then Update Orders marks it exported so the next poll skips it 5. Update Orders writes the carrier tracking number back onto the order line once the warehouse confirms 6. Orders held back for short stock post to the fulfillment lead with the SKU and the shortfall 7. The fulfillment lead decides whether to split the order, backorder the line, or offer a substitute ## What This Integration Enables Neto, now sold as Maropost Commerce Cloud, is the Australian all-in-one for retailers who run a webstore, a counter and a warehouse off one inventory rather than three. That single-inventory decision is what makes it worth automating: stock is tracked per warehouse and never as one global number, so the interesting work is not pushing rows around but keeping every channel honest about which shelf the goods are actually on. Its API has a property worth knowing before you build on it. Almost nothing in Neto can be deleted. Products, orders, customers, categories, warehouses, suppliers and content pages are all retired by turning a flag off, and there is exactly one delete route in the whole surface. That tells you what kind of system it is. Neto is a ledger of a trading business, not a content store, and agents working inside it are appending to a record other people will audit. FlowRunner agents read orders and carts, write stock and tracking, maintain the catalog and the supplier list, quote shipping against the store's own rules, and raise returns, with a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step wherever the write is one the API will never let anyone edit again. ### Without FlowRunner **The counter and the site disagree**: Stock is right in one place and stale in the other, and the gap is only found when an order cannot ship **Orders exported by hand**: Somebody exports a CSV to the warehouse each morning and remembers which rows already went **Returns handled in the control panel**: Refund decisions live in a staff member's head until they type them into a screen ### With FlowRunner **One stock figure per warehouse**: Supplier and warehouse feeds write stock per warehouse continuously, so the number the site quotes is the number on the shelf **Orders move on their own**: The poll picks up what changed, pushes it, marks it exported, and writes tracking back to the line **Returns decided with evidence**: The agent assembles the order, the window and the proposed refund split, and a person authorizes before it is written ## Use Case Scenarios ### Orders leave, tracking comes back The agent polls Get Orders on the update window rather than waiting for an event, because this API has no webhooks to wait for. Each new order is read with its lines, pushed to the warehouse or third-party logistics provider, and marked with Update Orders so the next poll ignores it. When the warehouse confirms dispatch, the agent writes the carrier and tracking number back onto the order line rather than onto the order, which matters because Neto splits and backorders lines independently and a customer chasing a partial shipment is asking about one line. Order data lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the operations dashboard, and anything the agent held back posts to [Slack](https://flowrunner.ai/integrations/slack). ### A supplier file becomes a stock level A supplier drops a stock file into a sheet or an inbox. The agent reads it with [Google Sheets](https://flowrunner.ai/integrations/google-sheets), maps each row to a SKU and a warehouse, and calls Update Stock Level in set mode so a full recount replaces the figure rather than adding to it. Products that appear in the file but not in the catalog are created with Add Products, priced, and placed in a category. Products that vanished from the supplier feed are not deleted, because Neto has no such route: the agent turns Active off and reports the list. The same loop can run against a counted stocktake instead of a supplier feed, and the effect is the same. Every channel the store sells through is quoting one number. ### A return request becomes a proposed RMA A customer emails about a faulty item. The agent finds the order with Get Orders, reads the lines and the payments already recorded with Get Payments, checks the purchase date against the store's returns window, and reads the customer's history with Get Customers. It then assembles the return authorization it would raise: which lines are coming back, what each line's refund subtotal would be, and whether shipping is being refunded too. It does not raise it. The proposal goes to the returns owner first, for the reason set out below. ## Human-in-Loop Highlight Neto publishes only two operations for returns. You can read them and you can add them. There is no update, no close and no delete, so an RMA written through this API is a permanent record with the status and the refund amounts it was born with, and the refund subtotal on each line is real money credited to a customer. Most systems treat a wrong refund record as a correction; Neto treats it as history. So the agent does all the work and stops at the write. It posts to the returns owner: "Order 18442, two lines returning. Line WIDGET-01 refund subtotal 89.00, line CABLE-03 refund subtotal 24.50, shipping refund 12.00, total 125.50. Purchased 31 days ago against a 30-day window. Raise this RMA?" The owner answers in the channel, the agent calls Add Returns with exactly what was approved, and the permanent record says what a person decided rather than what a rule inferred. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 42 actions ### Products and Stock 4 - **Get Products** Searches the catalog by SKU, brand, supplier, category or a change window, returning the fields the workflow asks for. - **Add Products** Creates products singly or as a batch, including variants placed under an existing parent SKU. - **Update Products** Updates products by SKU, merging nested collections such as categories and price groups rather than replacing them. - **Update Stock Level** Sets, increments or decrements the stock of one SKU in one warehouse. The most-used write in any Neto automation, and the one that keeps every sales channel honest. ### Orders 3 - **Get Orders** Searches orders by status, customer, SKU, payment or export state and a range of date windows. Polled on an update window, this is what stands in for the event feed the API does not offer. - **Add Orders** Creates an order with its lines, or a batch of them, for orders that were taken somewhere other than the Neto storefront. - **Update Orders** Changes an order's status, addresses, notes and export flags, and writes carrier tracking onto the individual order line. ### Customers and CRM 5 - **Get Customers** Searches customers by username, email, company, group or a change window. - **Add Customers** Creates customers singly or as a batch, keyed on the username that every later reference depends on. - **Update Customers** Updates a customer matched on username. Closing an account means turning Active off, because this API has no customer delete. - **Add Customer Logs** Appends CRM contact history to a customer, which is how a follow-up queue is built inside Neto. - **Update Customer Logs** Changes an existing log entry, typically to close out a follow-up an agent or a rep opened. ### Payments 3 - **Get Payments** Reads the payments recorded against orders by payment, order or paid-date window. Reconciliation reads this rather than the order, because one order can carry several payments. - **Add Payments** Records money received against an order. It books a payment rather than taking one, so it suits bank transfers and anything captured by another gateway. - **Get Payment Methods** Lists the store's configured payment methods with their accounting codes and active state. ### Shipping 2 - **Get Shipping Methods** Lists the store's configured shipping methods and who each one is visible to. - **Get Shipping Quote** Prices shipping for a destination and a basket using the store's own shipping rules rather than a formula maintained somewhere else. ### Catalog Structure 3 - **Get Categories** Reads the category tree by id, parent, name or visibility. - **Add Categories** Creates categories, placed under an existing parent or at the top level. - **Update Categories** Updates a category, including moving it, which moves its whole subtree with it. ### Content 3 - **Get Content Pages** Reads the store's CMS pages and posts by id, parent, type or change window. - **Add Content Pages** Creates a page or post, optionally letting Neto build the public slug from the name. - **Update Content Pages** Updates a page. Changing the slug changes the public address, so anything already linking to the old one breaks. ### Warehouses 3 - **Get Warehouses** Reads the store's warehouses with their references, addresses and primary flag. Usually the first call an inventory workflow makes, because every stock figure is keyed on one of these. - **Add Warehouses** Creates a warehouse. Marking a new one primary demotes the current primary, because a store has exactly one. - **Update Warehouses** Updates a warehouse. Taking one out of use means turning Active off, since stock already allocated to it stays there. ### Suppliers 3 - **Get Suppliers** Reads suppliers with their lead times, currency and account codes. - **Add Suppliers** Creates suppliers, keyed on a supplier code of your own choosing rather than an allocated number. - **Update Suppliers** Updates a supplier matched on that code. The code cannot be changed here, because products pointing at it would be orphaned. ### Vouchers 3 - **Get Vouchers** Reads vouchers and gift certificates with their remaining balance and usage history. - **Add Vouchers** Issues a voucher against a gift certificate line on an existing order, so the value and the program come from the product rather than the call. - **Update Vouchers** Changes a voucher's owner, contact email or redeemed flag. Marking it redeemed is how a voucher is voided. ### Returns 2 - **Get Returns** Reads return authorizations by order, customer, invoice, status or date window, including their lines and refunds. - **Add Returns** Raises a return authorization with its lines and refund amounts. This API has no update or delete for returns, so what is written here is permanent. It is the operation this page's human gate exists for. ### Carts 1 - **Get Carts** Reads carts by checkout status or date window, with the customer email and the restore link that puts an abandoned basket back. ### Store Settings 2 - **Get Currency Settings** Reads the store's default country, currency and tax rate. - **Update Currency Settings** Changes those store-wide defaults. They affect pricing and tax on every order, so this belongs in an occasional configuration flow rather than a frequent one. ### Accounting Mapping 4 - **Get Accounting Accounts** Lists the chart of accounts Neto holds for the linked accounting system, with each account's type and flags. - **Add Accounting Account** Adds one account from the linked accounting system to Neto's mapping table. - **Update Accounting Account** Changes one account in that mapping table, matched on the id Neto allocated. - **Delete Accounting Account** Removes one account from the mapping table. This is the only delete route the API exposes, it is irreversible, and it silently ends the posting path for whatever used it. ### Escape Hatch 1 - **Call API Action** Sends any action name and body to the store's endpoint, reaching parts of the API this connector does not name. The connector's defaults and validation do not apply here, so treat it as direct access rather than a modeled operation. ## Frequently Asked Questions ### What can FlowRunner do with Neto? FlowRunner agents can run Get Products, Add Products, and Update Products in Neto, plus 39 more actions. ### Does connecting Neto to FlowRunner require OAuth? No. Neto connects to FlowRunner with an API key, no OAuth flow required. ### Can Neto trigger a FlowRunner workflow automatically? Neto doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Neto?** This integration exposes Neto to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/neto. Site index: https://flowrunner.ai/llms.txt