Case Study
JPEC Eventos: an order portal that talks straight to the ERP
The partner builds the order in the catalogue and it lands in Omie with nobody retyping a thing.
The client
JPEC Eventos, founded in 2017, supplies ice cream from leading brands — Kibon, Ben & Jerry's and Bacio di Latte — to two channels: convenience markets inside residential buildings, which restock every week, and events, which buy by occasion. Its buyers are not end consumers: they are the building manager, the shop operator, the event planner. That changes everything — orders are recurring restocks, and they have to reach the ERP without anyone typing them in.
What the project called for
This is not an online shop: it is the buying channel of people who resell, wired into the system that issues the order.
An ERP failure cannot become the partner problem
The portal depends on an external system to close the order. If the ERP API is slow or down, the person buying cannot be left staring at a frozen screen, unsure whether the order went through.
The order must become an ERP order
A portal that only sends an email solves nothing: someone would still retype everything into Omie. The order has to be born inside it.
Volumes that do not fit item by item
Some operations arrive with dozens of orders at once, exported from another system. Typing them one by one is not an option.
Autonomy for the buyer
Partners need to log in on their own, see what they have already ordered and follow it — without calling the sales desk.
What we built
A .NET portal that is a buying catalogue and a bridge to the ERP at the same time.
Catalogue with search and browsing
Browsing by family and category and product search, so the partner quickly finds what they restock every week — and builds the order without relying on a printed list.
Orders straight into Omie
On checkout the order is transmitted to the Omie ERP and comes back with the number generated there. Nobody retypes: what the partner built is what entered the system.
Bulk import by spreadsheet
A whole batch of orders comes in through a spreadsheet. The reader locates columns by header name, so reordering them in the exporting system does not break the import.
Preview before transmitting
The batch is reviewed on screen before it goes out: what will be created, for whom and with which product. Only then is it sent.
TOTVS→Omie product mapping
An admin screen manages the translation from TOTVS product codes to Omie ones. If one item has no mapping, the batch is blocked instead of going up with the wrong product.
Guard against re-importing
The portal recognises a spreadsheet that has already been sent and refuses it before creating a single order — the same batch never goes up twice by accident.
A log of everything sent to the ERP
Each batch keeps a record of what was transmitted, item by item, with the Omie result. When something fails you can see exactly what — and resend just that.
Access invitation for partners
Registering a customer triggers an email invitation; the partner sets their own password and logs in. Records with more than one email get the invitation at all of them.
Order history per company
Whoever logs in sees the history of their company, not only what they placed themselves. Two people from the same shop see the same order.
Documentation and release notes inside the portal
The system manual and the list of what changed in each release live inside the product, maintained through an admin area. Users do not have to hunt for a stray PDF.
Platform always up to date
The portal gets continuous maintenance: updates applied and vulnerability fixes shipped as soon as they are disclosed, without waiting for the client to raise a ticket.
What is live
The fronts the portal supports today.
What it changes in practice
The effect of wiring the buying channel into the system that invoices.
The order is born in the right place
What the partner builds in the portal is what exists in Omie. The transcription step disappears — and transcription errors go with it.
Large batches stopped being a problem
One spreadsheet handles what used to be repeated typing, with an on-screen review before anything is created.
ERP errors surface instead of vanishing
A failure talking to Omie is recorded and shown to whoever ran the batch, with a per-batch log. Nothing disappears quietly.
Infrastructure and maintenance under contract
The portal runs on Amazon AWS and maintenance is ours: the people who look after the code look after the environment.
The best outcome of this project is an absence: the step where someone retyped orders into the ERP is gone — and typing errors went with it.
The services behind this project
It is the same work we do for other companies.
Do your customers still order by WhatsApp while someone retypes it into the ERP?
An order portal wired into your ERP takes the typing out of the middle and gives your sales team their time back. Tell us how your operation works today.