Warehouse shelving filled with boxes.

Home · Work · E-commerce

A retailer turned about 41,500 shipments into evidence for carrier negotiations

Case study · E-commerce · Warehouse and logistics

A pre-owned consumer electronics retailer lacked reliable live counts and clean carrier data. We redesigned SKU and bin control across 20,000+ products and turned about 41,500 shipments into negotiation evidence.

Client
A pre-owned consumer electronics retailer selling online and on marketplaces, with more than 20,000 products
Engagement
Warehouse SKU and bin control redesign, plus a carrier negotiation dataset built from six months of shipments
Result
A foundation for inventory visibility across 20,000+ products and about 41,500 shipments segmented by zone, weight and service
How we worked
Embedded with warehouse, fulfillment and HR managers, with each change tied to a buying or shipping decision

Published . Client name withheld.

41500Approximate shipments cleaned and segmented into a carrier negotiation dataset

The situation

The retailer sells pre-owned consumer electronics through its own web store and several marketplaces. Its warehouse handled thousands of used products, from consoles and games to accessories and bundles, and it had become a core bottleneck. Live counts were unreliable, SKU and bin control was inconsistent, and handoffs between procurement, fulfillment, quality checks, customer service and management reporting were not clean.

At the same time, last-mile shipping had become a major profitability lever as volume grew across channels. The business needed to negotiate with carriers on evidence rather than broad volume claims. What it had was a raw export from its shipping software covering about 41,500 shipments over six months.

What made it hard

  • This was not standard retail inventory. Condition, completeness, region, bundle composition and platform all changed what an item was, and marketplace SKUs did not always match what sat on the shelves.
  • Some products carried manufacturer barcodes and others needed internal ones, and storage and labeling had to avoid damaging game cartridges or adding impractical steps to handling.
  • Procurement decisions were made without strong warehouse validation, which raised the risk of repeat overbuying and fraud exposure.
  • The shipment export mixed carriers, services, stores, weights, addresses, fees and international records. The same warehouse appeared under two addresses in different systems, and billed weights, surcharge breakdowns and returns data were limited or missing.
  • The main carrier required 12 months of data and the retailer chose to proceed with six. Warehouse changes also had to move in step with SKU redesign, ERP development, procurement controls and customer service visibility.
A stack of red boxes on a table.

How we worked

We worked inside the operation with the warehouse, fulfillment and HR managers, and scoped the work around two decisions the business had to get right: what to buy, and what to pay to ship it. Every SKU rule, bin concept and data cut had to make one of those decisions better.

  1. 01

    Fix the data before the shelves

    Warehouse visibility started with data structure, not physical layout. We wrote a SKU policy that standardized product identifiers across the web store, each marketplace and internal systems, built to carry condition, completeness, region, bundle composition and platform. That structure became the base for bin-level control.

  2. 02

    Design bins around real handling

    We designed warehouse-facing barcode and bin concepts that used manufacturer barcodes where they existed and internal barcode logic where they did not. Where a label could not safely go on the item itself, as with fragile cartridges, we designed alternatives rather than force one method everywhere.

  3. 03

    Put warehouse truth into the ERP

    We connected warehouse visibility requirements to the design of the ERP modules then in development, so inventory visibility would sit in ERP workflows rather than in spreadsheets alone. We designed a warehouse validation check before repeat procurement, and supported weekly warehouse updates that informed procurement targets and leadership decisions.

  4. 04

    Build a carrier-ready shipment dataset

    We cleaned about 41,500 shipment records into a structured workbook with raw, lookup, clean and zone-mapping layers. Destination postal codes were normalized and mapped to carrier zones from the warehouse origin through formula-driven lookups, with zone rules and exceptions kept separate and visible.

  5. 05

    Negotiate on segments, not averages

    We segmented shipments by carrier, service, weight class, zone, origin and store, because blended averages hide where savings are realistic. International and other non-relevant records were held out of the main carrier’s quote analysis but kept for broader analysis and comparison across carriers.

The results

Measured against the outcomes agreed at the start.

41500
  • Laid the operating foundation for cleaner inventory visibility across more than 20,000 products.
  • Clarified SKU and bin logic, storage policy and the integration between the warehouse and the ERP.
  • Reduced reliance on fragmented spreadsheets as the main layer of warehouse control.
  • Turned an unstructured export of about 41,500 shipments into a carrier negotiation dataset, segmented by zone, weight class, service, carrier and origin.
  • Improved the retailer’s ability to model competing carrier offers realistically, instead of relying on headline rate tables.
  • Created a reusable analytics base for future requests from carriers for 12 months of shipment data.

What leaders can take from it

  • Warehouse control in a used-product business starts with data structure, not physical layout. SKU and bin logic has to be designed with the people who handle the products, or it will not survive contact with the shelf.
  • Carrier negotiating strength comes from clean shipment evidence, not total volume. Segmenting by zone, weight and service shows carriers your real profile and shows you where savings are realistic.
  • Find missing fields such as billed weight, surcharges and returns early, because they limit how accurate a negotiation can be. A clean data room makes every carrier conversation more credible.

Questions about this work

What shipping data do you need before negotiating with carriers?

You need shipment-level data segmented by zone, weight class and service, not blended averages or total volume. For a pre-owned consumer electronics retailer, Armstrat cleaned about 41,500 shipments from six months of history, normalized destination postal codes, mapped them to carrier zones and separated international records. Find gaps such as billed weight, surcharges and returns early, because they limit negotiation accuracy.

How do you get inventory control in a used-goods warehouse?

Start with the data structure, then the shelves. Used products vary by condition, completeness, region, bundle and platform, so the SKU has to carry those differences before bins and barcodes can work. Armstrat wrote a standard SKU policy across the web store, marketplaces and internal systems, designed bin and barcode concepts around fragile items, and connected warehouse visibility to the ERP design.

Bring us the hard problem.

We agree the outcomes first, then work inside your business until they hold.