Custom Warehouse Management APIs and Software for the floor you already run, and the systems that cannot reach it.
We build warehouse management systems, the APIs that let everything else read and write to them, and the ERP, EDI and carrier integrations in between.
Most of this work starts with a WMS that already runs the floor and cannot be reached from anywhere else. We are a custom development partner rather than a WMS vendor, so the answer is often to keep the system and build the interface.
- 120+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 5.0Unified rating across 61 client reviews on Clutch
- 2 to 4 weeksTypical time from signature to start
- ISTQBCertified QA inside every sprint
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
What warehouse software has to do, from the dock door to the ERP
Custom warehouse management software is the system that runs a building, plus the interfaces that let everything else read it: a WMS covering receiving through dispatch, and the APIs, ERP, EDI and carrier integrations that keep the business in step with what is on the shelf. unicrew builds and extends both halves, as part of our wider logistics and transportation work. We publish four case studies here, each client with a Clutch review: Bitergo, MiniMoves, Cloud Van Lines and Mover Technologies.
- Receive and put awayFrom the truck at the dock to stock in a location the system believes in.
- Inbound and ASN handling
- Putaway and location rules
- Cross-docking and returns
- Store, count and pickWhere the floor lives, and where a wrong number costs a customer.
- Inventory and location control
- Cycle counting and adjustments
- Pick, pack and dispatch
- Talk to everything elseThe half nobody budgets for: ERP, storefront, carriers, trading partners.
- REST APIs and webhooks
- EDI: 856 ASN, 940, 945
- GS1 barcodes and SSCC labels
- See and proveOne number the floor, finance and the customer can all be shown.
- Stock accuracy reporting
- Chain of custody trails
- Exception and audit logs
02Compare
Extend the WMS you run, or replace it
Almost every enquiry here arrives framed as a replacement, and about half are not one. The question is narrow: is the pain the system, or is it that nothing can talk to the system? The second is an integration project, not a migration, and the two differ by an order of magnitude in cost and risk.
| What the floor is telling you | What it usually costs | The route that fits |
|---|---|---|
| “Nothing can read the WMS without a nightly file.” | Every integration is a batch job, on yesterday’s data | An API layer in front of the system you already run: read models first, then the writes your partners need.Platform development and integrationOr book a meeting |
| “The WMS is fine. It is the reporting people complain about.” | Nothing, and a replacement would | Keep the WMS. A reporting layer over its data costs a fraction of a migration and nobody retrains the floor.Reporting and data engineeringOr book a meeting |
| “The website says two in stock and the shelf says none.” | Oversells, refunds, a manual count every week | One stock service both sides read, with reservations and a reconciliation path that explains a difference rather than hiding it.Where this bites in e-commerceOr book a meeting |
| “Everything the warehouse produces is re-keyed into the ERP.” | Two records of one movement, neither trusted | A custom layer between the two, so the ERP is fed by events instead of by somebody’s evening.Custom ERP for logisticsOr book a meeting |
| “No WMS we have seen handles the way we actually pick.” | Fighting the product on every release | Build. Here a custom system costs less over its life than bending someone else’s data model around your floor.How we build custom systemsOr book a meeting |
03Solutions
The six pieces of warehouse work we are actually asked for
Each names the situation it is right for, because most are wrong for most warehouses. Two are builds. Four go around a system that already works.
A documented interface in front of a system that has none: stock, orders, movements and events, reads first.
- Right when
- The system works and nothing can reach it
Receiving through dispatch, built around your layout, your SKUs and your peak, when no packaged option fits.
- Right when
- Your picking logic is how you compete
One stock service the storefront, the marketplace and the floor all read, with reservations and a reconciliation path.
- Right when
- Two systems hold two stock numbers
EDI documents in and out, ERP postings driven by warehouse events, carrier APIs for rates, labels and status.
- Right when
- Orders arrive by file and leave by hand
Barcode and mobile flows designed around gloves, cold stores and a device that has to survive a shift.
- Right when
- The floor is the slowest surface you own
Stock accuracy, pick rates, dwell and exceptions in one place, on a schedule your team can plan against.
- Right when
- The weekly number is assembled by hand
How we take access, and what we are certified in
Contracts and NDAs before anyone starts, then least-privilege access agreed with your technical contact and no write access to production during discovery. Delivery runs with ISTQB-certified QA engineers inside the sprint. unicrew holds ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK.
04Stack
What we build with, and what we connect to
The stack behind the platforms below, plus the ERPs we configure, extend and connect. Those ERP names come from our wider logistics and ERP work, not from a warehouse build. Send your integration list with the enquiry and we will say what is realistic before you commit.
Angular
React
Storybook
iOS
Android
- REST API
ASP.NET- ASP.NET MVC
- .NET
Java
PHP
AWS
Azure
Odoo- ePROMIS
- Microsoft Dynamics 365
Sage 300- NetSuite
Replacing a working WMS is among the riskiest things an operation can do: the cutover happens on a live floor with real stock on it. Usually the pain is not the WMS but that nothing can talk to it. An interface in front of the system you already run is smaller, reversible, and often removes the reason to replace it.
Ihor PrudyvusDelivery Director, unicrew05Delivery
How a warehouse engagement runs without stopping the floor
Four stages, shaped by one constraint: the floor cannot stop, and a bad release is felt within the hour by someone holding a scanner. So the first thing we ship cannot write anything. Most engagements start within two to four weeks of signature.
- Walk the floor, then read the interfacesReceiving, a pick round, a cycle count, and the exceptions people have quietly built a workaround for. Then the same operation seen from the WMS database, the ERP and the files between them.You getA map of the operation and every interface it leans on
- Read-only first, alwaysThe first thing we build reads and never writes: a stock view, an exception report, an API that answers questions. It cannot break a shift, and it settles whether the system or the integration is the problem.You getA read-only interface running against your live data
- Write paths, one area at a timeWrites go live by area or by wave, alongside the current process until the floor stops double-checking them. Nothing goes in during peak, and the old path stays standing.You getWorking software in one area, with the old path intact
- Cutover, then hand overThe last area moves, the parallel process retires, and the documentation goes to whoever runs the system on nights, which is rarely the team that commissioned it.You getA system your own team can run, and the runbook for it
06Proof
What these clients said afterwards, in their own words
Three published builds, three named clients. One is a warehouse-management software company; the other two are the order and operations layer a warehouse talks to, and we would rather say which is which.
- A warehouse software company's own productBitergo in Dortmund sells Warehouse Star, a cloud WMS. We rebuilt its Business App Store front-end on Angular, with Storybook components shared across 15+ applications, then integrated the backend over REST. Managing director Andreas Trautmann writes on Clutch: "After launching the site we saw a rapid increase of test accounts ordered by potential customers" and "Now the site provides a steady source of sales leads".15+apps sharing the component set we built
- The order system a moving operation runs onFor MiniMoves in Chicago we work on the order management system the business sits on, which CFO and VP of IT Jeff Sides says "handles everything from lead management to accounting". In his 2022 review he writes that the enhancements "increased productivity and allowed us to maintain double digit growth without a substantial increase in staffing".Double digitgrowth held without a substantial increase in staffing
- A platform written from nothing, still being extendedCloud Van Lines in Boston: a SaaS for household moves. CEO Jeff Chizmas writes: "Artelogic wrote the platform from scratch", "We started the project in December 2016", and "the platform is integrated with smart containers that allow users to get data and information on their shipping containers, like the location at any given time". He is describing work done under our former Artelogic brand.2016the year this build started, in the client's words
07Case studies
Three builds, and what each one had to leave running
Three starting points: a front-end rebuild inside a live product, an order system nobody could take offline, and a platform written from nothing.
See all case studies
LogisticsApp Store for warehouse managementOur client Bitergo offers a collection of business apps to optimize warehouse management, scalable from start-ups to 4PL companies. Given the business drivers, the client decided to upgrade the front-end of all their applications to the latest version of Angular.Rapid increaseOf test accounts ordered by potential customers after the site launched
LogisticsMiniMoves Orders Management PlatformA custom-built moving order system that simplifies booking, boosts automation, and improves operational efficiency.Double digit growthMaintained without a substantial increase in staffing
LogisticsCustom software for USA moving companyAn end-to-end SaaS platform for managing household moves and every business operation of a logistics company.Built from scratchAn end-to-end SaaS for household moves and the operations behind them
08Questions
Questions buyers ask before they commit
Supply chain management decides what should be where and when; the warehouse system records what actually is, and tells everything upstream and downstream about it. That is why the interface matters as much as the system: a WMS with perfect internal data and no usable API leaves the ERP, the storefront and the carrier working from a number that is hours old.
If stock is recorded correctly and the complaints are about reporting, integration or a workflow nobody can reach, that is an interface project, and an API layer costs a fraction of a migration. Replace when the data model is wrong, when the vendor has stopped shipping, or when your picking logic is how you compete. Otherwise keep the WMS and spend the money on the integrations that hurt.
Yes, and it is the most common shape of this work. Reads before writes: a documented read API over stock, orders, movements and events, then the write paths your partners need. Where the WMS exposes nothing usable, the interface is built against its database or its file drops and versioned separately, so a product upgrade does not take your integrations with it.
Yes, and that half is usually the larger one. On the trading-partner side: EDI documents in and out, including the advance ship notice and the warehouse shipping order and advice, plus GS1 barcodes and SSCC pallet labels. On the ERP side we build the layer that posts warehouse events instead of somebody re-keying them; unicrew configures, extends and connects Odoo, ePROMIS, Microsoft Dynamics 365, Sage 300 and NetSuite.
Three engagement models: time and materials billed hourly and quoted per project, fixed price quoted per project against an agreed outcome, and team extension billed monthly per team member. We recommend one at the end of discovery, not before. We do not publish a project price band: a read-only stock API and a custom multi-site warehouse system are too far apart for one to mean anything. No recruitment or placement fee on team extension, and fixed-scope work carries a post-launch warranty agreed in the contract.
Most engagements start within two to four weeks of signature. After that the floor sets the pace: the first read-only interface is deliberately small and goes in early, write paths follow area by area alongside the existing process, and nothing goes live during your peak. We would rather say at scoping which quarter a cutover is realistic in than promise a date that lands in November.
Contracts and NDAs before anyone starts. Access is least-privilege, agreed with your technical contact, read-only where the work allows, and never write access to production during discovery. Delivery runs with ISTQB-certified QA engineers, and unicrew holds ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK. We do not hold SOC 2, and say so rather than let you assume it. Staff data (scanner logins, pick rates) makes GDPR retention a data-model decision we take early.
Before you commit to a WMS replacement, get a second opinion
A call with a senior engineer who has shipped warehouse and order-platform work, not a sales qualifier. You leave with an opinion on extend or replace.
What happens after you contact us
- We reply within one business dayA senior engineer reads your message, not a bot.
- A call about the floorWhat you run, what cannot reach it, and where the counts drift.
- Route and engagement model, in writingExtend, integrate or build, priced as time and materials, fixed price, or team extension.
- NDA, then discoveryMost engagements start within two to four weeks of signature.