Retail and omnichannel
Your omnichannel operation doesn't fail in its systems. It fails between them.
Point of sale, e-commerce, order management, ERP and invoicing each work on their own; no one owns the thread that ties them together. Hábil works on that thread: integration and orchestration for omnichannel retail.
Prefer email? Write to us at hola@habil.mx
A badly built integration doesn't crash
It answers correctly and leaves the data wrong. A system that replies "accepted" to an incomplete message raises no alarm: it produces a sale recorded without any items, a close that doesn't balance, or an invoice that was never issued. The damage surfaces weeks later, at reconciliation or audit, and by then it is no longer an isolated case. That is why Hábil works in the integration and orchestration layer — the one that coordinates every other system — and sells none of the pieces.
Symptoms your operation already knows
Each symptom hits one executive first.
"I sold it, and the ERP doesn't know."
Orders that leave the channel and never reach the financial system, or reach it and the response is never recorded.
Sales and FinanceSales that exist for the customer but not for the company: they are neither invoiced nor collected.
"The books don't balance, and no one knows whose problem it is."
The value of the items doesn't match what was collected; each team points at the other and the report arrives weeks late.
FinanceRevenue that doesn't reconcile with collections, and closes that get reopened.
"Everything says yes."
Services that reply "accepted" to an empty or incomplete message, because they validate the format and not the content. There's no error, no alert, and the data ends up wrong.
TechnologyNo visible errors, no alarm; the defect lives until someone goes looking.
"The tax document depends on a response that may never arrive."
Issuing the invoice requires a piece of data returned by another system, with no guaranteed deadline and no one watching whether it came.
CEOA tax risk that shows up on no dashboard and surfaces at audit.
"It stopped halfway."
An outage leaves the operation half done: the system treats it as complete and the work never happened.
SalesOrders that seem to move forward and are actually stuck.
And others your technical team will recognize: operations no one can trace, events arriving out of order, retries that freeze errors, repeated messages, configuration living outside the code.
Why now?
Because these defects give no warning: they show up in peak season, during an ERP change, at year-end close or in an audit — exactly when fixing them costs more.
Processes we master
These are business processes before they are technology. Several look like variants of the same thing, and they aren't: each variant leaves a different document and a different accounting entry, and mixing them up is what throws the close out of balance.
Omnichannel order lifecycle
Capture, confirmation, inventory allocation, picking, shipping and delivery — and every outcome that doesn't end in "delivered". Every order moves only through the allowed steps and, above all, never through the ones that aren't.
Fulfillment options, each with its own rules
Home delivery, in-store pickup, ship-from-store, in-store sales from the whole network's inventory (extended catalog) and marketplace sales. Each one changes who charges for shipping, which document is issued, which warehouse ships the goods and when revenue is recognized.
Returns: not one process, but several
It changes depending on where the item was bought, where it's returned and whether the sale is already in the global invoice; each combination carries its own document.
What happens at the counter, in every system
In-store receiving, handover and returns, reflected in the channel and in the ERP.
Cancellations, shortages and losses
Cancellation before and after shipping, partial or total shortage, failed or incomplete delivery, theft or loss in transit, and credit without product return. Each case produces a different document and a different accounting entry; mixing them up is a frequent cause of reconciliation discrepancies.
Mexican e-invoicing (CFDI) and tax compliance
Invoice at the point of sale, periodic global invoice, invoicing after the global invoice, re-invoicing for incorrect data, credit notes for returns and, for imported items, integration with the import documents the invoice must reference. Here we mean integrating the tax flow that already runs between your systems.
Accounting and financial integration
Every commercial event leaves its entry in the ERP, with the right sign and period, and the merchandise amount reconciles against what was collected.
Modernizing legacy integrations
Legacy integrations no one dares to touch because there's no way to test them: every change is a risk and every new rule, a project. We make them safe to change: every new rule goes out tested, in stages and without shutting the operation down.
Coexistence and transition between ERPs
During an ERP change, two systems tell the truth at the same time — and each tells it differently: reconciliation depends on knowing which one rules for each transaction. An ERP change doesn't start from zero: coexistence is designed before the change, not after.
What we offer
Where each order is and which document it has in each system, in a single query.
Search with the number your team already uses, and every step leaves evidence your auditor can review.Every order in a valid state, even when it doesn't end in "delivered".
All your systems read each order's step the same way, even when a rule changes.A message that can't be right doesn't go out.
It stops in red before reaching the ERP or the invoicing system.Differences between channel and ERP caught in time, not at the close.
No manual reconciliation between channel and ERP.Correcting a submission without duplicating it.
Resending doesn't duplicate the sale or hold up the fix.Every step of the flow auditable, without exposing personal data.
You see what happened at each step, and personal data is protected throughout the whole journey: encrypted in transit and masked in the logs.Legacy integrations you can test and version.
Changed in stages, without fear of breaking them and with the operation running.Existing integrations stabilized, including those built by another provider.
Starting here means you don't decide blind: what the assessment finds defines what's worth doing next.
Also as a platform
If you prefer not to build from scratch, Hábil MDW comes with the order model, inventory with reservations, shipments, invoicing and seven messaging channels, and the flow is adjusted to your operation through configuration.
How we work
In stages, with the operation running. First we measure what each integration does today; then we replace one segment at a time, and each segment is tested before it replaces the previous one. Nothing is switched off to modernize.
The Hábil modular platform
We don't replace your ERP or your point of sale. When your operation needs a piece it doesn't have today — or has, but can't count on — we add it with our own components that connect to what is already working. You take the piece you need, not the whole platform.
For retail
- Inventory by location. Stock per store and warehouse; holds with an expiry so the same unit isn't sold twice; authorized transfers; a movement history no one can alter. Who gets the last item is decided by the system, not by luck.
- Scheduling and reservations. Resource, time slot and place — an appointment, a delivery window, an installation — with temporary holds, rescheduling and no-show records. A cancelled slot is released immediately.
- Multichannel notifications. Immediate or scheduled notices and reminders that arrive even when a provider fails: if one doesn't respond, the notice goes out through another, and each one is recorded with its trail.
- Online payments and recurring billing. Charge by card or payment link without your systems ever touching card data; issue refunds, handle disputes and know why each attempt was declined. Recurring billing is authorized once and can be paused and resumed, with a retry schedule after a decline. What sets this piece apart: it knows whether the money moved. A charge whose confirmation never arrived is held until it's cleared up, instead of being taken as good or blindly repeated.
Integration. Each piece notifies the others when something changes, and repeating an operation doesn't duplicate it.
Trust. Every operation leaves a trail you can query months later, who changed it is recorded, and personal data stays out of technical logs.
Flexibility. Rules, prices and texts are adjusted through configuration, without reprogramming and without waiting for a deployment.
Mexican e-invoicing (CFDI)
Invoice at the point of sale and global invoice to the general public, on the schedule you define. The recipient's tax data is validated before issuing, without wasting an invoice number (folio). Cancellation with the official reasons, with the replacement invoice issued and linked. Credit notes linked to their original invoice. Delivers XML and PDF. And it works with more than one authorized certification provider: if one doesn't respond, the invoice is issued through the other, and an invoice is never stamped twice, even when a confirmation doesn't arrive. It issues Mexican payment complements (complemento de pago: the CFDI that records each payment on a sale paid in installments or later), invoices carrying the Mexican customs information of imported items (the import data the CFDI must include), and the replacement invoice already linked to the one it cancels.
Design principle
Your business decisions — what happens, when and to whom — stay yours, and changing them is a matter of configuration, not reprogramming. That is why the platform doesn't age like a hand-built integration.
Scope: Point-of-sale integration, promotions and loyalty, and order management beyond the sales flow are not platform modules: they are delivered as an integration and orchestration service.
The assessment, in two levels
First conversation, at no cost.
The map of your integrations — which system talks to which, in what format, and who owns each segment — and the three points where information is probably being lost.
In-depth assessment, with read access to your integrations and an agreed scope.
Which reconciliation discrepancies are live today and where they come from, which tax risks to address first, and a staged stabilization path.
The scope is agreed in the first conversation.
We work under confidentiality; that's why you won't see client names here. Nor will you see yours on anyone else's page.
We work with a few clients at a time: the architect who reviews your assessment stays with your project all the way through.
FAQ
What people ask us before starting
No. We work in the layer that connects them: integration and orchestration. You keep the systems you already have, and the thread between them becomes reliable and traceable.
Yes. It's the natural starting point: first we measure what each integration does today, including those built by another provider, and then decide what to keep.
No. We work in stages, with the operation running.
In the first conversation, at no cost: the map of your integrations and the three points where information is probably being lost. In the in-depth assessment, with read access: live reconciliation discrepancies and their origin, prioritized tax risks and a staged path. The scope is agreed in the first conversation.
No. Its modules solve specific mechanisms — inventory by location, reservations, notifications, payments and e-invoicing — and connect to the systems you already have.
Don't see your question?
Start by knowing where you stand. Message us on WhatsApp and tell us which systems coexist in your operation.
Prefer email? Write to us at hola@habil.mx
A named case, on our case studies page:
Arteaga JoyeríaDoes the question that comes up at eleven at night have an answer?
Hábil AI