Convex
Logistics software & systems integration

Software for the shipments your systems don't connect.

We help logistics providers and shippers connect WMS, TMS, ERP, carriers and customers — and automate the manual work in between.

Warehouse · Transport · Visibility · Integration · AI

WMS
TMS
ERP
Carriers
Customers
Operational workflow
The visibility gap

Every system knows a part of the shipment.

Warehouses, transport systems, carriers and customers each hold a piece of the picture. The work that matters — a late pickup, a short delivery, a customs hold, a disputed invoice — crosses all of them.

We build the software that connects them.

That means extending what you already run — WMS, TMS, ERP, carrier portals — not proposing another platform to replace it.

WMS
TMS
ERP
Carriers
Customers
Operational workflow
Today, that gap is often filled by
ExcelEmailPhoneCopy/pasteManual reportsApprovalsTribal knowledge
Follow the shipment

Follow the exception.

Logistics systems are optimized around the planned flow. The cost shows up when a shipment doesn't go according to plan.

  1. Order
  2. Inbound
  3. Warehouse
  4. Pick & pack
  5. Carrier pickup
  6. In transit
  7. Delivery
  8. Invoice
What if

Carrier misses the pickup.

One deviation from the plan. Here is what often happens next — without software that connects the dots.

  1. 01Customer asks where the shipment is
  2. 02Support checks the TMS
  3. 03Calls or emails the carrier
  4. 04Checks the warehouse for the pallet
  5. 05Re-books another carrier
  6. 06Updates the delivery slot
  7. 07Informs the customer
  8. 08Adjusts the invoice by hand
The expensive part of logistics is rarely the shipment that arrives on time. It's the one that doesn't.

What happens in your operation when a shipment doesn't go according to plan? Tell us about it.

Where we help

Where logistics friction becomes software opportunity.

Warehouse operations & WMS integration

Problem
Receiving, putaway and picking run in the WMS, while inventory corrections and exceptions live in spreadsheets and chat.
Intervention
Connect the WMS with ERP, carriers and customer systems, and automate the manual steps around receiving, picking and inventory accuracy.
Outcome
More accurate stock, fewer manual corrections, faster order cycle times.

Transport & carrier coordination

Problem
Booking, dispatch and tracking are spread across emails, carrier portals and phone calls.
Intervention
Bring carrier booking, status updates, delay detection and re-planning into one workflow connected to your TMS.
Outcome
Delays caught earlier, less time chasing carriers, proof of delivery on file.

Inbound & supplier visibility

Problem
Supplier delays and their inventory impact are usually discovered one phone call at a time.
Intervention
Bring supplier status, advance shipping notices, delays, inventory implications and procurement actions into one workflow.
Outcome
Inbound decisions made on current information, not yesterday's.

Customs, documents & billing

Problem
Shipping documents, customs paperwork and freight invoices are assembled and reconciled by hand, shipment by shipment.
Intervention
Generate and validate documents from shipment data, and reconcile carrier and customer invoices against what actually moved.
Outcome
Fewer holds and disputes, faster invoicing, audit-ready records.

Customer visibility & reporting

Problem
Customers ask where their goods are, and operations teams build the answer from exports.
Intervention
Give customers and internal teams one current view of shipments, exceptions and service levels, built from your existing systems.
Outcome
Fewer status requests, and numbers you can trust.

Legacy & system integration

Problem
WMS, TMS, ERP, EDI links and carrier APIs don't talk to each other, so people do it by hand.
Intervention
Connect existing systems, APIs and EDI flows without replacing what already works.
Outcome
Existing investments keep working — together.
AI in logistics operations

An AI front desk for transport requests.

Built for road-freight operators, where requests arrive by email and can wait hours for a first answer. The front desk reads each one, understands it and answers within minutes — with people staying in charge.

  1. Receive request
  2. Understand
  3. Look up price
  4. Draft reply
  5. Human in control
  6. Send
  7. Audit
Example — a customer emails a transport request

The system extracts

  • Pickup and delivery places
  • Dates and time windows
  • Goods and quantity
  • Language of the sender
  • A confidence and a quoted source for every detail
Then it
  • Looks up an indicative price in the operator's own price list
  • Drafts an acknowledgement saying what it understood
  • Asks once for anything that is missing
  • Says honestly when a lane has no listed price
  • Sends only when sending is enabled and the recipient is approved
  • Records every action

One console for the dispatcher

Requests, email threads, extracted details, indicative price, drafted reply and audit trail in one place — no retyping into another system.

Romanian and English

Replies are drafted in the sender's language from templates the operator approves, so wording stays consistent and on-brand.

Operations lead in control

Switch between shadow and live mode, manage the recipient allow-list, import the price list and review what the agent did.

Corrections and recovery

Correct a misread request and reissue the reply, or recover a request that got stuck, without losing the history.

Honest about what it doesn't know

Missing details are asked for once. Lanes without a listed price get a clear "no price" instead of a guess.

Built to grow

Email first. The same core extends to further channels and to TMS, telematics and freight-exchange integrations.

The system never sends a final quote and never confirms an order. Dispatchers keep the decisions; the front desk removes the waiting and the retyping.

Shadow mode firstRecipient allow-listModel reads, never pricesReplies from approved templatesEmail treated as untrusted inputFull audit trail
Before / after

An architectural change, not a marketing one.

The same operational workflow, with and without a connecting layer between systems.

Before
  1. TMS
  2. Excel
  3. Email
  4. Phone call
  5. Carrier portal
  6. Manual report
After

ERP Convex operational layer WMS / TMS / carriers / customer systems

  • Workflow automation
  • Exception detection
  • Unified context
  • Approvals
  • Notifications
  • Decision support
  • Audit trail
How we engage

Start with one workflow.

Convex doesn't ask you to begin with a large transformation programme. We start with one workflow that creates disproportionate manual work, and prove value there first.

  1. 01

    Map

    Understand one problematic logistics workflow: systems, people, carriers, data, manual steps, exceptions and delays.

  2. 02

    Identify

    Find where software can create the highest operational leverage — prioritized by business impact, frequency, feasibility and effort.

  3. 03

    Pilot

    Build a focused solution around one high-value problem, integrated with your real systems and run first in shadow mode.

  4. 04

    Expand

    Once proven, extend from one workflow to a team, a warehouse or lane, and additional sites.

  1. Diagnostic
  2. Pilot
  3. Production
  4. Expansion
A focused starting point

Operational Workflow Diagnostic

Show us one operational workflow that creates disproportionate manual work. Convex works with operations and IT to understand:

  • How the process actually works
  • Which systems are involved
  • Where humans intervene
  • Where information is duplicated
  • Which exceptions create delays
  • Where automation could produce measurable value
Output — Operational Automation Map
  • Current workflow
  • Systems and dependencies
  • Major friction points
  • Automation opportunities
  • Recommended target architecture
  • Prioritized interventions
  • Proposed pilot
Why Convex

Complex operational problems need more than another application.

Convex is a boutique engineering consultancy, able to move from an ambiguous operational problem through discovery, architecture, implementation and production operation — with senior engineers involved throughout.

Enterprise architectureSoftware engineeringSystem integrationAI & automationProduct thinking

That includes production-grade systems, complex integration, modernization and observability — brought to bear on operations, not just customer-facing software.

Financial servicesBorder control & public sectorAutomotiveManufacturingLogisticsRetailE-commerceMarketplacesData-intensive systems
Also see

Making the goods as well as moving them?

Manufacturing software & integration

Show us one shipment flow that shouldn't still work this way.

If an important logistics process still depends on spreadsheets, email, carrier phone calls or people moving information between systems, we'd like to understand it.

Discuss a logistics bottleneckhello@convex.consulting

30-minute exploratory conversation. No transformation programme. Start with one real workflow.

We use cookies to understand how visitors use this site. We only set analytics cookies if you accept.