Start with the business and technical reality
Warehouse integrations sit close to the customer promise. If stock is wrong, customers buy unavailable products. If order release fails, fulfilment stops. If split shipments are not returned correctly, the customer sees inaccurate status. This makes operational visibility essential.
We clarify what “stock” means before synchronising it. Physical on-hand, allocated, quarantined and available-to-sell are different concepts. The website normally needs a commercial availability value, not every internal warehouse quantity. Likewise, order states need to reflect whether an order has merely been sent, accepted, allocated, picked or shipped.
The integration is designed around these states, with explicit recovery for rejects, cancellations and partial fulfilment.
When clients bring us in
- Website availability does not match warehouse reality
- Orders occasionally fail to reach the warehouse
- Tracking data is delayed or incomplete
- Split fulfilment creates incorrect customer status
- Cancellations arrive after picking has begun
- Manual warehouse reconciliation consumes significant staff time
What good delivery should leave behind
A successful engagement should improve more than the immediate feature or incident. It should make the system easier to understand, safer to change and more visible to the people responsible for operating it.
- Clear technical ownership and responsibilities
- Maintainable code and configuration
- Visible failures rather than silent data loss
- Controlled release and recovery paths
- Documentation for future developers and operators
- A sensible next-step roadmap rather than permanent firefighting
Technical depth across the parts that matter
The exact scope depends on the existing environment and commercial priorities. We focus on the areas that materially affect reliability, maintainability and delivery rather than adding process for its own sake.
Inventory
Transform warehouse availability into the sellable quantity required by the commerce platform.
Order release
Send complete, validated orders with the identifiers and delivery data the WMS requires.
Acceptance
Record whether the WMS accepted or rejected the order and expose exceptions quickly.
Fulfilment
Return pick, pack, shipment, split and tracking events to commerce.
Cancellations
Define when a cancellation can be accepted and what happens once warehouse processing has begun.
Reconciliation
Compare orders and stock across systems and recover missing transactions safely.
Common failure patterns that create unnecessary cost
Many technical problems are recurring patterns rather than isolated defects. Identifying them early helps avoid repeatedly paying to treat the visible symptom.
- Raw on-hand stock exposed as sellable stock
- Orders marked as sent but never acknowledged by WMS
- Shipment updates overwriting partial fulfilment state
- Tracking numbers attached to the wrong shipment
- Retries producing duplicate warehouse orders
- No visibility of rejected lines or warehouse exceptions
A controlled route from uncertainty to production
We prefer visible, reviewable delivery. The exact sequence changes with the project, but the principle is to reduce uncertainty early and keep each production change understandable.
Technology is part of the answer, not the starting question
The interface can use APIs, queues, webhooks or files. The main design priority is preserving order state and making exceptions visible quickly enough for operational teams to act before the customer experience is affected.
Where specialist capability comes from our wider engineering team, we are transparent about the proposed delivery model and match the person or team to the actual requirement rather than presenting a long list of technologies as if every project needs all of them.
Use the level of ownership that fits your team
Defined project
Midoriweb owns an agreed scope with clear milestones, acceptance criteria and release responsibilities.
Specialist workstream
Bring us into one technically difficult area while your existing team or agency owns the wider programme.
Team augmentation
Add developers to your existing process for a fixed period or an ongoing roadmap.
Ongoing technical partner
Combine support, maintenance, monitoring and planned improvement under continuing technical ownership.
Questions worth answering before work starts
Can you integrate a WMS with Magento Open Source?
Yes. Magento/WMS integration is a common part of our connected-commerce work.
How often should stock sync?
That depends on transaction volume, overselling tolerance and WMS capability. Some environments need near-real-time updates; others are reliable with short scheduled intervals.
Can split shipments be supported?
Yes, provided the WMS can expose line-level fulfilment and tracking information.
What about click-and-collect or multiple warehouses?
These can be supported where source-system data and allocation rules are clear.
How do you recover missing shipments?
We design reconciliation and replay routes so missing transactions can be identified and recovered without duplication.
Can you replace an existing fragile integration?
Yes. We can document current behaviour and transition individual flows in stages.
Continue exploring
Have a requirement in this area?
Send the current situation, desired outcome, platform or systems involved and any important deadline. We can review the detail first or discuss it in a short consultation.