3PL & B2B Logistics · Houston, TX

The systems that move your freight, finally talking to each other.

Your WMS knows what's on the shelf. Your TMS knows what's on the truck. Your ERP knows what it cost, and your customer's EDI feed knows none of it. Stone Age Software builds the integrations, workflows, and portals that close those gaps — so your team stops re-keying orders and starts shipping them.

To be clear: we're the software team, not the 3PL.

We don't warehouse your inventory or haul your freight. We build and support the technology that lets the people doing it run leaner — whether that's a single-site warehouse getting off spreadsheets or a multi-client 3PL onboarding its next big-box account.

Capabilities

Six places logistics software quietly leaks money

Each of these starts as a manual workaround somebody built once to survive a busy week — and then never got to remove.

WMS & Warehouse Operations

Receiving through shipping, on a scanner instead of on paper and spreadsheets.

  • Receiving, putaway, pick/pack/ship & cycle-count workflows
  • Barcode, RF, and mobile screens built to be used wearing gloves
  • Multi-client inventory separation for 3PL operators
  • ZPL label & packing-slip printing, including print-and-apply

TMS, Rating & Freight Routing

Rate-shop, tender, dispatch, and track loads without re-keying a thing.

  • Parcel, LTL & FTL carrier API and rate integrations
  • Load tendering, dispatch boards & check-call automation
  • Tracking, ETA, and proof-of-delivery capture
  • Accessorial and detention capture at the moment it happens

EDI & Trading-Partner Onboarding

New retailer or customer? Mapped, tested, and live without the chargebacks.

  • X12, EDIFACT, and RosettaNet PIP mapping, order through cash
  • AS2, SFTP, VAN, RNIF/ebMS, and REST/webhook transports
  • Retail routing-guide compliance & 997 acknowledgements
  • Chargeback root-cause analysis and prevention

Order & Inventory Orchestration

One source of truth across every warehouse, channel, and your ERP.

  • Multi-node inventory, allocation & backorder rules
  • Marketplace, webstore, and B2B portal order intake
  • ERP and accounting sync (NetSuite, Dynamics, QuickBooks)
  • Dropship, kitting, lot/serial tracking, and RMA flows

3PL Billing & Freight Settlement

Bill every storage, handling, and accessorial charge you actually earned.

  • Rate engines for storage, handling & value-added services
  • Automated customer invoicing straight into accounting
  • Carrier invoice audit and reconciliation against quoted rates
  • Margin and cost-to-serve reporting per customer

Customer Portals & Visibility

Give customers a login instead of giving your team another phone call.

  • Branded 3PL portals for inventory, orders & documents
  • Dashboards for OTIF, dock-to-stock, fill rate & cost per order
  • Exception alerting on stuck orders and failed EDI
  • Scheduled reporting customers stop having to ask for
Who we build for

If freight, inventory, or purchase orders touch it, we've probably wired it

3PLs & fulfillment centers

Multi-client operations that need each new customer onboarded fast and billed correctly.

Freight brokers & forwarders

Tendering, tracking, and back-office automation that keeps margin visible per load.

Warehouse operators

Public, contract, and cold-storage sites moving off paper, whiteboards, and spreadsheets.

B2B distributors & wholesalers

EDI-heavy order flows, big-box retail compliance, and ERP integration that holds up.

Manufacturers & shippers

Inbound supplier ASNs, plant-to-DC moves, and freight spend you can finally audit.

Brands scaling into retail

Going from a webstore to Walmart, Target, or Amazon vendor requirements without panic.

Two ways in, depending on what hurts

Most logistics operations have one of two problems. Either the warehouse floor is running on paper, tribal knowledge, and a spreadsheet nobody else can open — or the floor is fine, and the pain is every trading partner demanding files in their own format on their own schedule.

They need different fixes, so we've written them up separately. Start with whichever one sounds like your Monday morning.

Signals it's the warehouse

Mis-picks climbing with volume, cycle counts that never reconcile, and a supervisor who is the only one who knows where anything actually is.

Signals it's the integration

Someone re-typing orders from a PDF or portal, retail chargebacks you can't explain, and inventory that's accurate in one system and fiction in the other.

Signals it's the billing

Accessorials that never make it onto an invoice, storage billed off a month-old snapshot, and no honest answer to which customers are actually profitable.

How an engagement runs

Prove it on one lane before you bet the network on it

  1. 1

    Map the flow

    We walk the actual path of an order — every system, hand-off, email, and workaround — and put numbers on where the hours go.

  2. 2

    Pilot one partner

    One customer, one lane, or one document type goes live first. Small enough to be safe, real enough to prove the payback.

  3. 3

    Roll it out

    Then it becomes a template. Each additional partner or site reuses the mapping, the tests, and the runbook.

  4. 4

    Watch it run

    Monitoring and alerting on every feed, so a failed transmission reaches you before it reaches your customer.

Engagement models

Priced for operators, not enterprise procurement

We're a small, senior team by design. You get the engineer doing the work, and a scope you can start without a steering committee.

Integration assessment

Fixed fee · 1–2 weeks

We map every system, hand-off, and manual workaround in your flow, then hand you a prioritized plan with effort and payback per item. Yours to keep, whoever builds it.

Scoped build

Fixed scope · per project

One integration, one partner, one workflow at a time — priced up front. Most first engagements are a single EDI partner or one system-to-system link.

Fractional integration team

Monthly retainer

Ongoing capacity for partner onboarding, carrier changes, peak-season prep, and the monitoring that catches a failed transmission before your customer does.

Integration targets

Platforms, formats, and partners we build against

Working with something not on this list? It's usually still a documented API, a flat file, or a database — all three of which we speak.

NetSuite Dynamics 365 BC SAP IDoc Acumatica Epicor QuickBooks Extensiv / 3PL Central ShipHero Fishbowl Cin7 Infor WMS MercuryGate McLeod Turvo Tai project44 Descartes ShipStation EasyPost FedEx / UPS / USPS APIs SPS Commerce TrueCommerce Cleo VAN interconnects Shopify Amazon SP-API Walmart Supplier One X12 & EDIFACT RosettaNet PIPs AS2 / SFTP Samsara

Listed as systems we integrate with. Names are the property of their owners and imply no partnership, certification, or endorsement.

Questions we get

Straight answers

Are you a 3PL?

No — we are the software team behind 3PLs. We build, integrate, and support the systems logistics operators run on. If you need warehouse space or a carrier, we are not that. If your WMS, TMS, ERP, and trading partners do not talk to each other, that is exactly what we do.

Do we have to replace our WMS or TMS?

Almost never. Most of what hurts in a logistics operation is the gaps between systems, not the systems themselves. We start by integrating and automating what you already own — and we will tell you honestly if a platform genuinely has to go.

How fast can you onboard a new EDI trading partner?

On a document set we have already mapped for you, typically days. A brand-new retailer with its own routing guide, labeling rules, and certification process is usually two to four weeks, most of which is their testing cycle rather than our build.

Can you work with our VAN, or do we need one?

Either way. We work through existing VANs and translators, and we can also run direct AS2 or SFTP connections and modern REST/webhook APIs where a partner supports them — which often trims per-character VAN fees along the way.

What happens during peak season?

We plan around it: load-test before Q4, freeze risky changes through peak, and stay reachable for the cutover-sensitive weeks. We would rather ship an integration in August than firefight it in November.

We are a small operation. Is this worth it?

Often more so. A single-site 3PL with three EDI customers loses just as many hours to manual re-keying as a large one, with fewer people to absorb it. We scope small fixed-price pieces so you can see the return before committing to more.

Bring us your worst hand-off.

Tell us the one place your order flow falls apart. The assessment is free, and the plan is yours either way.

Start the conversation