Supply chain optimization built onto what you run
We work on the logistics software you already run. Assess what is there, integrate and modernize it, automate the steps people still do by hand, then add AI where the data supports it. 100+ senior in-house engineers across six countries, on the market since 2012.
The work starts on the systems you already run, not beside them. The same team built Jack Cooper's vehicle-inspection platform, supporting 9M+ vehicles.
- 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
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
What we change on a stack that already runs
Supply chain optimization software is the tooling that gives a logistics operation visibility, automation and forecasting over its own shipments, orders and stock. We build it onto the systems you already run rather than beside them: assess what is there, integrate and modernize it, automate the manual steps, then add AI where the data supports it.
02Proof
What each of these clients already had
- Jack Cooper: inspections in the fieldA cross-platform vehicle-inspection system on iOS, Android and web, taking field inspections digital for one of the largest US automotive-logistics providers. Read the case study.9M+ vehicles supportedthe scale of Jack Cooper's own operation, which has managed inventory and inspections on well over 9 million vehicles
- MiniMoves: a bought platform, made to fitA new order-management platform, built by customizing a base .NET product rather than writing one from scratch, with unicrew hired as the primary development team. Read the case study.Double digit growthmaintained without a substantial increase in staffing, in the client's own words, Clutch review 14288 (March 2022)
- Bitergo: a warehouse suite, with a new front endThe front end of a warehouse-management application suite, rebuilt on Angular with a reusable component library so the next application is cheaper to build. Managing Director Andreas Trautmann names the product in Clutch review 18113: "Warehouse Star is a cloud based warehouse management system for e-commerce, retail and industry." Read the case study.Start-up to 4PLone app platform, scaled across both ends of that range, from the case study's own published description
03Problems
Three problems that put an operation on this page
Named the way they get named on a first call: visibility, manual work, and cost you cannot trace. They are three different pieces of work, each routed to the service that does it, and the third is usually the one that has to wait for the other two.
Custom dashboards and predictive analytics for full operational transparency, built on what your own systems already produce. Where a status is missing, the fix is upstream in the feed rather than in the chart.
Automation tools and system integrations to eliminate bottlenecks: entering an order, rating a shipment, assigning transportation, and the status update a customer telephones in to ask for.
AI route optimization and demand forecasting to reduce waste, once the history behind them is complete enough to train on. Where it is not, that is the first piece of work.
What these builds actually run on
Across the five logistics builds named on this page: ASP.NET, ASP.NET MVC, .NET, Java, PHP, JavaScript, React, Angular, Storybook, REST API, Xamarin, iOS, Android, AWS and Azure. The Jack Cooper engagement used Angular. We work in the stack the operation already has, because a rewrite into a different language is a decision somebody should make on purpose rather than inherit.
04Compare
Buy a platform, build from zero, or change what you run
Three routes: buy a packaged platform, build a custom system from zero, or modernize and extend what already runs. Which fits turns on how much of your process is genuinely different. One carrier and a shared spreadsheet makes a custom build premature, and until somebody says which system owns the shipment record, all three routes inherit the argument.
- unicrew
Modernize and extend what you run
Today's system stays up: the integrations and the modules that hurt most are replaced first, so dispatch and the warehouse keep working through the change. What you own at the end is the systems you already paid for, joined and extended, plus a custom layer over the part of the process that is actually yours. What it asks for: an assessment that reads somebody else's decisions and says plainly which modules to keep, which to wrap and which to rebuild.
- Today's system
- Stays up through the change
- You own
- What you paid for, extended
- What it asks
- A clear read of what to keep
- Off the shelf
Buy a packaged platform
Today's system is replaced, and the process is re-cut to match the product. Standard workflows land quickly; the ones you compete on come back as configuration. What you own at the end is a subscription, and your data inside somebody else's schema; extending it means whatever the vendor's extension model allows. What it asks for: customization wherever your process differs. MiniMoves bought a base .NET system with basic transportation functionality, and we customized it around an operation that works differently from other moving companies. The purchase was the start of the work.
- Today's system
- Replaced, re-cut to the product
- You own
- A subscription and a schema
- What it asks
- Work that starts at the purchase
- Greenfield
Build a custom system from zero
Today's system runs until the new one is finished, so you carry both and reconcile between them for the length of the build. What you own at the end is exactly the workflow you specified, and every line of it to maintain. Cloud Van Lines took this route and got an end-to-end SaaS for household moves, written from scratch. What it asks for is time: a greenfield platform is judged against something that already works, so it reaches parity before it can be better, and parity is the expensive part.
- Today's system
- Runs alongside the build
- You own
- Every line you specified
- What it asks
- Reaching parity first
05Client story
What replacing a running system looked like at MiniMoves
Replacing without rewriting
Replacing an order-management system does not have to mean writing one. MiniMoves bought a base .NET product with basic transportation functionality, then hired us to make it fit an operation that, in his words, works a bit differently from other moving companies. The system was redesigned and refactored around that model rather than rebuilt from nothing.
About 3,000 to 4,000 moves a year
Jeff Sides, VP of IT at MiniMoves, sets out the scale in Clutch review 43900: "We service all 50 US states, have partners in all of the major metropolitan areas, and do about 3,000–4,000 moves each year."
What the bought platform covered
He describes it in the same Clutch review: "We had an outdated custom-built order management system that we needed to replace with new technology." The base .NET system they bought covered entering an order, rating a shipment and assigning transportation; the rest of the operation is what needed the customization.
Hired as the primary development team
What he hired us to do, in Clutch review 43900: "We hired Artelogic to customize the system and serve as our primary development team." And what that turned out to be: "Artelogic assisted us in redesigning and refactoring the base order management system to fit with our model." The relationship began under our former Artelogic brand.
Double digit growth without substantially more staff
His later Clutch review, 14288, is the one quoted in the reviews further down this page: the order platform became the system the business would not function without, and the enhancements since, in his own phrase, maintained double digit growth without a substantial increase in staffing. Double digit is his hedge, and it stays one.
The same pattern, from the other end
Cloud Van Lines' platform was written from scratch, and it did not stay as written. Jeff Chizmas, its CEO, in Clutch review 50724: "Since the initial development, we've modified the software as the market has changed. Now 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." One project began by customizing a purchase, the other by writing a platform, and neither ended where it started. That is the shape of software modernization work on an operation that cannot stop while it changes.
We deliver supply chain optimization as a sequence. First we agree the system of record and join your systems, so one shipment has one status. Then we automate manual data entry, and the forecast comes last, trained on history you can trust.
Oleksandr TrofimovCTO & Co-Founder, unicrew, who leads our transportation and logistics work06Process
How the work is sequenced
Four stages, and the order is not a preference: each one tells you whether the next is worth doing, which is why route optimization sits behind the integration that feeds it. Much of the assessment's value is deciding which of the remaining three your operation needs, and in what order. Most engagements start within two to four weeks of signature.
- Assess what runsWe read the systems, the data and the handoffs with the people who use them: what the platform you bought actually covers, where a spreadsheet is doing load-bearing work, and which feeds fail quietly. The output separates what is worth keeping from what is only a reporting problem.You provideAccess to the systems, and an hour each with the people who run dispatch, the warehouse and the back officeYou getA written map of the stack, the data and the gaps, with a recommended order of work
- Integrate and modernizeThe platform you already run, the carrier data you quote from, and the systems that hold your orders, joined so one shipment has one status. Module by module, in the order the assessment set, so the operation keeps running while it changes.You provideAPI credentials, a test environment, and one person who can decide which system owns a recordYou getWorking integrations in production, and platform work you can extend
- Automate the manual stepsQuoting, order entry, status updates and the report somebody rebuilds every Monday. Each one is measured against the hours it currently costs before it is built, so the sequence is argued from your numbers rather than from ours.You provideThe current process in full, including the workarounds nobody has written downYou getAutomated workflows in front of the staff who run them
- Add AI where the data supports itRoute optimization and demand forecasting last, because both are models and a model is only as good as the history behind it. Where the data needs work, we fix the feeds first, so the model trains on history you can trust.You provideShipment history, and a decision on what a good forecast would changeYou getA model in production when the data is ready, plus the data work that gets it there
07Integration
Where the integration work actually is
Under the screen everybody looks at
Most of the work in a supply chain build sits in the layer where several systems have to agree about where one shipment is. The visible part is only as true as what feeds it, which is why the assessment reads the feeds before anyone designs a dashboard. Logistics APIs versus custom integration argues buy, build and blend at article length; if you are still deciding whether any of this is worth doing, the role of logistics in supply chain management is the ground floor.
A live-quote engine, in the founder's words
Mover Technologies is the example on this page: a freight-management platform, iOS and Android apps for two audiences, and a live-quote engine that pulls carrier data in real time. It is at beta stage, in the founder's own account. Boruch Akbosh, in Clutch review 115841: "For the last 5 or 6 months, we have been working on a new calculator which allows our beta tester to go in and generate live quotes by collecting data from each dealer, and also by pulling API data from freight companies." On the two apps, in the same review: "We have apps for iOS and Android for both customers and dealers." Our round-up of logistics APIs for the supply chain industry lists what is available before you decide to build.
After the long run
Handing the layer under your operation to a partner is a long-term decision, so the review worth reading is the one a client writes after years rather than after the launch. Akbosh, in the same Clutch review: "I have been working with them for many years. Artelogic is my number one resource, especially for projects of such magnitude." He wrote Artelogic because that is the brand we traded under when he hired us. Three neighbouring pages go deeper than this one should: freight API development covers building and consuming carrier APIs, custom ERP for logistics covers the build specifics when the system of record is an ERP, and logistics and transportation carries the vertical argument and the platform catalogue behind it.
08Case studies
Three builds, one for each route above
The same three options, each with a client who took it. MiniMoves customized a platform it had already bought, Bitergo had the front end of an existing app suite rebuilt, and Cloud Van Lines had the whole thing written from scratch.
See all case studies
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
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
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
09Reviews
Reviews from the operations we build for
Our business simply wouldn’t function without the Order Management system. We have made numerous functional and performance enhancements that has increased productivity and allowed us to maintain double digit growth without a substantial increase in staffing.
After launching the site we saw a rapid increase of test accounts ordered by potential customers. Now the site provides a steady source of sales leads.
I’m consistently humbled by Artelogic’s performance. Projects of this caliber are hard to outsource. Teams come and go, and this type of work almost never gets done. They’ve kept their priorities straight as they’ve grown and always deliver.
They’re a highly ethical and well-managed organization. I was amazed by the CEO’s skill level and business acumen.
I’ve been impressed by their work ethic and how they put me as the customer first. They’re always ready to jump in and go the extra mile. They put great effort into communicating to ensure that tasks are updated in a timely manner. The team keeps us apprised of exactly what they’re working on.
10Facts
Who you would be handing the operation to
The facts a procurement form asks for, in one place inside the page rather than in a footer. The Clutch rating and review count above are as of 31 July 2026.
- The companyFounded in 2012, and trading as Artelogic until the rebrand.
- 100+ senior in-house engineers across six countries
- Five offices: Ukraine, Poland, Estonia, the UK, and a US business address in Ormond Beach, Florida
- 120+ projects across 12 countries since 2012
- Certified, and auditedBoth certifications renewed through a multi-stage audit with Quay Audit UK.
- ISO 27001:2022 for information security
- ISO 9001:2015 for quality management
- ISTQB-certified QA engineers on the delivery team
- GDPR and NIS2 govern how operational data is handled
- How it startsThe two dates a buyer asks about before anything else.
- Most engagements start within two to four weeks
- Inbound enquiries are replied to within 1 business day
- Three engagement models, billed as set out in the first answer below
11FAQ
Questions worth asking before you commit an operation to a build
Three engagement models: time and materials (billed hourly, quoted per project), fixed price (outcome based, quoted per project), and team extension (billed monthly per team member). unicrew quotes each engagement on its own scope, because the number turns on how many systems have to be joined, what state the data is in, and how much of the process is genuinely yours. There is no recruitment or placement fee on a dedicated team or team extension: nothing separate is charged for sourcing, vetting or placing an engineer. On how that compares with hiring, Jeff Sides of MiniMoves in Clutch review 14288: "They are very cost effective. We could not have the same level of expertise through internal hires." Which model suits which shape of work is argued out in time and materials versus fixed fee.
Most engagements start within two to four weeks of signature. What ships first is decided in the assessment, and it is usually the workflow costing the most hours rather than the one that demonstrates best. The delivery date comes out of scoping, because a date given before anyone has read the systems is a guess. On an operation that cannot stop, a wrong date costs more than a late answer.
Usually not, and the assessment is what decides it. MiniMoves kept the base .NET product it had bought and had it redesigned and refactored to fit its own model. Bitergo kept its application suite and had the front end rebuilt on Angular with a reusable component library. Where a platform genuinely cannot carry a process, we say so in writing and sequence the replacement module by module, so the operation keeps running throughout. The build specifics when the system of record is an ERP are on custom ERP for logistics.
They are the first thing read and the last thing thrown away. The assessment maps every feed and every integration before anything is built, because a dashboard is only as true as what fills it, and a feed that fails quietly is fixed before anything is layered on top of it. unicrew is ISO 27001:2022 and ISO 9001:2015 certified, renewed through a multi-stage audit with Quay Audit UK, and GDPR and NIS2 govern how operational data is handled.
Yes, in the order that makes it work. Route optimization and demand forecasting are models, and a model is only as good as the history behind it, which is why AI is the last of the four steps here rather than the first. Where the shipment history is incomplete or inconsistent across systems, we repair the feeds first, then train the model. What that step involves once the data supports it is set out on AI integration services.
An inventory of the platforms and feeds in play, where the data is thin, which workflow is costing the most hours, and a recommended order of work with the reasoning attached. It is written to be read by the person who runs dispatch as well as by whoever signs it. Where keeping what you have and repairing two feeds is the right call, that is what it recommends.
When the process you compete on is your own and runs across systems that have to work as one. Nothing we earn depends on which platform you buy, so the recommendation follows your operation, and where a packaged system fits part of the process, we integrate it. When the team can work with you remotely, since our engineers are spread across six countries. And when the operation runs on more than one carrier and system, which is the joining work this page describes.
Show us the operation, get a straight answer
Tell us where the operation leaks time or money. We will tell you what we would change on the stack you run, what we would leave alone, and in what order, in writing.