Hundreds of invoices a month, none of them typed
An Automation flow issues the invoice for every confirmed order with its series and its register; bulk and recurring issuing are shipped.
Partial coverage
Vertical
ERP for online shops
Invoicing every order, reconciling what the gateway pays out and automating the paperwork already work; the catalogue and the stock are the verticals still missing.
An online shop needs a catalogue, orders, stock and invoicing. In iERP, Finance — invoices, credit notes for returns, payments and bank reconciliation — and Automation, which turns every confirmed order into its invoice with nobody typing, are shipped. Ecommerce — catalogue, orders and store integration — and Inventory — stock, warehouses and valuation — are declared in the catalogue and cannot be activated yet.
The day to day
The day-to-day it solves
What piles up in the back office of an online shop, and which part iERP covers today.
The return that has to be credited properly
Credit notes, refunds and partial payments are handled in Finance, with the chained register behind them and without editing an already issued invoice by hand.
Reconciling what the gateway pays out
The gateway's grouped payouts are reconciled against the bank statements inside Finance, instead of exporting everything to a spreadsheet every Monday.
Not selling what you do not have
Real-time stock and the catalogue are Inventory and Ecommerce, the two pending verticals. Today stock is controlled elsewhere and what enters iERP is the money of the order.
The modules that cover it
The modules that cover the online shop
Every card carries its real status and its page, so you can check for yourself which part is usable today and which is still coming.
Ecommerce
On the roadmap
Online catalogue, orders and store integration with inventory and invoicing.
View module
Inventory
On the roadmap
Warehouses, stock, movements and valuation, wired to purchasing and sales.
View module
Finance
In production
Invoicing with your own series, partial payments, treasury forecasting and a chained invoice register.
View module
Automation
In production
Flow canvas, triggers and steps with human intervention across modules.
View module
An example from the vertical
An order pipeline, run by the AI
The request whoever runs the shop would make, and what the agent does with it.
The agent works with the permissions of whoever speaks to it, asks for confirmation before writing and leaves a trail of every action.
379 published actions an agent can execute in iERP.
Automate the invoice for every confirmed order.
automatizacion.flujo_crear flow in draft
I have prepared the flow that invoices every confirmed order; it is left as a draft so you can review it and switch it on when you want.
- How much have we invoiced this month and how much has already landed in the bank?
- Prepare the credit notes for this week's returns.
Partial coverage
What is not there yet
Two are missing: Ecommerce — catalogue, orders and store integration — and Inventory — warehouses, stock and valuation. They are declared in the product catalogue and cannot be activated in a workspace yet. Invoicing and the flows that fire it, on the other hand, work today with Finance and Automation. If you need the verticals, tell us: we prioritise by real demand.
Questions about ecommerce
What people ask before booking a demo.
Not out of the box yet: store integration is part of the Ecommerce vertical, declared and not activatable. What does work today is the money side — invoice, credit note, payment and reconciliation — and the Automation flows that fire it.
Shall we look at your orders?
Half an hour on your day to day: what you can use now and what would wait for the vertical.
Available in: Professional