Freight and 3PL Controls in Global Shop Solutions

Executive Summary

Global Shop Solutions is built around the shop floor and the sales order, not the freight contract. Its shipping module records the carrier, the bill of lading and the ship-via code against a sales order, and its AP module runs a standard three-way match of purchase order, receipt and invoice. Neither step reads a carrier rate schedule, a fuel surcharge index or an accessorial tariff, because the system has no field built to hold one.

The mechanism that causes leakage is specific: three-way matching confirms an invoice matches a PO in quantity and unit price, not that a freight line's rate, minimum charge or surcharge matches the underlying carrier agreement. A freight invoice for a correct shipment can still carry a wrong rate, a stale fuel surcharge or an accessorial charge the contract does not permit, and the ERP has no rule that would stop it.

What changes it is not a bigger ERP module. It is a control layered on top: a rate card and surcharge schedule checked against every freight invoice before it posts. That check is what Global Shop Solutions was never built to run, and freight cost movement documented by BLS PPI data makes the gap more expensive every quarter it goes unchecked.

1. What does Global Shop Solutions actually track on an outbound shipment?

Global Shop Solutions ties each outbound shipment to a sales order, recording the ship-via code, the carrier name, and the bill of lading number as part of the shipping transaction. That record confirms a shipment happened, against which order, and through which carrier. It does not carry a rate table, a lane-specific contract rate, or a fuel surcharge formula, because the shipping transaction documents movement of goods, not the freight charge that follows it.

The shipping module's job is operational: pick, pack, ship, and record proof that an order left the dock. That is what a warehouse team needs, and Global Shop Solutions does it as a routine part of order fulfillment.

What it does not do is hold the commercial terms a freight invoice should be checked against. There is no native field for a negotiated rate per lane, no fuel surcharge index reference, and no accessorial fee table tied to a specific carrier contract. The shipment record and the freight invoice live in different systems conceptually even when they sit in the same database: one documents that a truck left, the other bills for it.

That separation is normal ERP design. It becomes a control gap only when nothing downstream closes it, which is the case here.

2. How does the AP module match a freight invoice before payment?

Global Shop Solutions AP applies a standard three-way match: the invoice is checked against the purchase order and the goods receipt for quantity and unit price agreement. For a freight invoice tied to a PO, that confirms the invoice references a real transaction and that a header amount lines up with what was ordered. It does not test whether the freight rate, minimum charge, or surcharge calculation on that invoice conforms to the actual carrier contract, because the match logic.

Three-way matching is a real control, and it catches a meaningful class of errors: an invoice for goods never received, a quantity mismatch, a price that does not match the PO line.

Freight invoices frequently arrive without a clean PO in the first place, since freight is often billed after the fact by weight, lane, and accessorial rather than against a pre-priced purchase order line. Where a PO exists, matching confirms the header total, not the components: base rate, fuel surcharge percentage, and each accessorial charge on the invoice.

An invoice can pass three-way match cleanly while still charging a fuel surcharge percentage that is stale relative to the index the contract specifies, or an accessorial fee for a service the contract does not list. The match was never designed to look inside the freight calculation.

3. Can Global Shop Solutions catch a stale fuel surcharge on its own?

No. Global Shop Solutions has no field or rule that stores a fuel surcharge index or recalculates a surcharge percentage against current fuel data at invoice entry. The AP clerk keys the invoice amount as presented by the carrier, and the system posts it once it clears the three-way match.

Whether the surcharge percentage reflects the fuel index the contract actually references is a question the ERP never asks, because it has nowhere to keep the answer.

A freight contract's fuel surcharge clause ties the surcharge percentage to a published fuel index, reviewed on a schedule the contract sets. Gasoline PPI data (US Bureau of Labor Statistics, Producer Price Index, series WPU0571, read 2026-09-06) shows the July 2026 index at 302.759, up 37.1% year over year, which is the scale of movement a surcharge clause is meant to track over time.

Global Shop Solutions has no mechanism that references that kind of index or recalculates what a surcharge should be this month versus last. The surcharge line on an incoming invoice is data entry, not a calculation the ERP checks. If a carrier's surcharge percentage lags a falling index or overshoots a flat one, the ERP posts the invoice as presented.

Catching that requires a control that reads the invoice's stated surcharge percentage, holds the index the contract cites, and flags a mismatch. That control sits outside the ERP.

4. Does Global Shop Solutions enforce contracted freight rates by lane or carrier?

No native module in Global Shop Solutions stores a carrier rate card by lane, weight break, or accessorial schedule, so there is nothing in the system to enforce a contracted rate against an incoming invoice. The shipping module confirms a carrier moved a shipment; the AP module confirms an invoice references a valid transaction. Neither step holds the negotiated rate table that would let the system flag an invoice charging above the agreed rate for that lane and weight break.

The gap here is structural, not a missing report someone forgot to configure. It follows directly from what the vendor master and shipping transaction are built to hold.

A. What the system holds instead

The vendor master in Global Shop Solutions holds a carrier's name, address, and payment terms, the standard fields any AP vendor record needs. It does not hold a rate table structured by origin-destination lane, weight break, or service level, and there is no report that compares an invoiced rate against such a table because the table does not exist in the system.

B. What this means for a rate increase

General freight trucking PPI data (US Bureau of Labor Statistics, series PCU484121484121, read 2026-09-06) put the July 2026 index at 195.575, up 8.1% year over year, showing rates moving broadly. A carrier passing along an increase beyond what a specific contract permits would post through Global Shop Solutions unflagged, since nothing in the system compares the invoiced rate to the contracted one.

5. What kinds of freight drift slip through as a result?

Three drift types recur on freight invoices moving through an ERP without a rate control layer: a base rate above the contracted lane rate, a fuel surcharge percentage that no longer matches the index the contract specifies, and an accessorial charge for a service the contract does not authorize or caps at a lower amount. None of the three fails a three-way match, since each concerns the composition of a charge rather than whether a PO and receipt exist.

Each of these is a mechanism, not a frequency claim: the invoice's calculation departs from the contract's calculation, and no step in Global Shop Solutions is built to compare the two.

The truck transportation of freight PPI (US Bureau of Labor Statistics, series WPU3012, read 2026-09-06) put the July 2026 index at 170.984, up 10.9% year over year, context for how much a rate or surcharge error compounds when the underlying cost base is also moving.

• Base rate drift: A per-mile or per-hundredweight rate above the negotiated lane rate, invisible to a match that only checks PO quantity and price header.
• Surcharge drift: A fuel surcharge percentage set by the carrier's own schedule rather than the index the contract cites, compounding over every shipment on that lane.
• Accessorial drift: Detention, liftgate, or residential delivery fees billed without the conditions the contract requires to trigger them, or above the capped amount.

6. Should a manufacturer add a rate audit control, or replace Global Shop Solutions?

Replacing an ERP to gain freight rate enforcement is disproportionate: Global Shop Solutions runs the shop floor, inventory, and order fulfillment well, and none of that is broken. The gap is narrow and specific, sitting entirely inside AP's freight invoice review step. A control that checks each freight invoice's rate, surcharge, and accessorial charges against the actual carrier contract closes it, without touching production scheduling, inventory, or the rest of the ERP.

The decision is not ERP versus no ERP. It is whether AP has a step, manual or automated, that reads the carrier contract and checks the invoice against it before payment. Today that step does not exist inside Global Shop Solutions, and building it as a spreadsheet exercise means someone maintains a current rate table, a current surcharge index, and an accessorial rule set by hand for every active carrier lane.

A fixed-scope diagnostic answers a narrower, cheaper question first: how much of the last 12 to 18 months of freight spend already reflects margin drift. That answer establishes whether building or buying an ongoing control is worth the cost, before committing to either.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

7. Frequently Asked Questions (People Also Ask)

Does Global Shop Solutions have a freight audit module?

No. Global Shop Solutions has a shipping module for recording shipments and an AP module for three-way matching. Neither is built to hold a carrier rate card, a fuel surcharge index, or an accessorial fee schedule, so there is no module that checks a freight invoice against the underlying contract.

Why does a freight invoice pass three-way match if the rate is wrong?

Three-way matching checks that an invoice references a real PO and receipt and that a header amount lines up with what was ordered. It does not decompose a freight invoice into base rate, surcharge, and accessorial lines and compare each against the carrier contract, so a wrong rate inside a matched invoice goes uncaught.

Can we add a fuel surcharge index field to Global Shop Solutions ourselves?

A custom field can store a number, but the ERP has no logic that recalculates a surcharge percentage against that index or compares it to what a carrier invoices. Closing the gap requires a control process, not just a data field, that reads the invoice, holds the current index, and flags a mismatch before payment.

Does Global Shop Solutions track freight by lane or weight break?

The vendor master holds a carrier's name, address, and payment terms. It does not hold a rate table structured by origin-destination lane or weight break, so there is no basis in the system for comparing an invoiced rate against a contracted one for a specific lane.

What is the difference between a shipping record and a freight rate control?

A shipping record documents that a shipment happened: carrier, ship-via code, bill of lading. A rate control checks whether the charge on the resulting invoice matches the contract. Global Shop Solutions produces the first. Nothing in the system produces the second.

Should we build a spreadsheet to track freight contract terms instead?

A spreadsheet can hold rate tables and surcharge indexes, but someone has to update it by hand for every active carrier lane, and it has no connection to the AP posting process, so a stale spreadsheet still lets a bad invoice post.

Does accessorial drift show up anywhere in Global Shop Solutions reporting?

Accessorial charges post as part of the invoice total the AP module records. The system has no field distinguishing a valid accessorial charge from one the contract does not authorize, so nothing in standard reporting isolates accessorial drift from the rest of the invoice.

Is this gap specific to Global Shop Solutions or true of ERPs generally?

The mechanism described here, three-way matching without a rate schedule reference, is a function of what a shipping and AP module are built to record, not a defect unique to one vendor. Any ERP built around PO and receipt matching rather than contract terms carries the same structural gap on freight.

What does a margin drift diagnostic actually check on freight invoices?

It matches each freight invoice's base rate, fuel surcharge, and accessorial charges against the carrier contract, rather than against the PO and receipt the ERP already checks, to identify where the invoice and the contract diverge.