Supply Chain and ERP Buyer's Glossary
Plain-English definitions of the contract, compliance and operational terms buyers run into when evaluating ERP, warehouse, transport, procurement and fleet software.
- Accessorial charges
- Fees carriers add on top of base linehaul rates for extra services or conditions, such as detention, liftgate, residential delivery or waiting time. Clear accessorial schedules in contracts are essential for cost control.
- Continuous transaction controls (CTC)
- Tax regimes in which invoice data must be reported to, or cleared by, the tax authority in or near real time, as in India, Saudi Arabia, Mexico, Brazil and a growing number of European countries. They directly affect ERP and procurement software choices.
- Cutover
- The planned sequence of steps that moves a business from its old system to the new one, including final data loads, open-transaction migration and the go/no-go decision. It is usually rehearsed several times before go-live weekend.
- Data residency
- A requirement, set by law, regulation or contract, that certain data be stored or processed within a specific country or region. Buyers should confirm which hosting regions a SaaS vendor offers and where backups and support access sit.
- Electronic Data Interchange (EDI)
- A standardized format for exchanging business documents such as purchase orders, invoices, load tenders and shipment status between trading partners. Common standards include ANSI X12 and UN/EDIFACT, and many carriers and retailers now also offer APIs.
- Fit-gap analysis
- A structured comparison of your required business processes against a system's standard functionality, classifying each as fit, configurable or gap. Gaps then get resolved through process change, extensions or third-party add-ons.
- Freight audit and payment
- The process, often outsourced, of checking carrier invoices against contracted rates and shipment data before paying them. It catches duplicate billing, rate errors and unapproved accessorial charges.
- Hypercare
- A period of heightened support right after go-live, typically four to twelve weeks, when the implementation team stays on hand to fix defects and stabilize operations. Its length and staffing should be written into the contract.
- Load tendering
- Offering a shipment to a carrier, usually through a TMS, EDI or API, for acceptance at an agreed rate. Tender acceptance rates are a key measure of carrier reliability and routing-guide health.
- Master data
- The core reference records a system depends on, such as items, customers, suppliers, locations and charts of accounts. Poor master data quality is a leading cause of failed go-lives across ERP, WMS and TMS projects.
- Named user vs. limited user license
- A named or full user license lets one specific person use the system's full functionality, while limited, team or self-service licenses cost less but restrict which transactions a user can perform. Getting the mix right is one of the biggest pricing levers in ERP negotiations.
- Peppol
- An international network and set of document standards for exchanging electronic invoices and other procurement documents through certified access points. It is used or mandated for e-invoicing in many European and Asia-Pacific countries.
- Renewal price cap
- A contract clause that limits how much a SaaS vendor can raise subscription fees at renewal, usually expressed as a fixed percentage or tied to an inflation index. Without one, renewal increases can significantly erode a negotiated discount.
- Sales and operations planning (S&OP)
- A recurring cross-functional process that balances demand forecasts with supply, inventory and financial plans to agree a single operating plan. S&OP software supports scenario modeling and consensus workflows.
- Service-level agreement (SLA)
- The contractual commitment a vendor makes on uptime, support response times and issue resolution, often with service credits if targets are missed. Buyers should check how uptime is measured and what exclusions apply.
- Slotting
- Deciding where each SKU is stored in a warehouse based on velocity, size, weight and pick patterns. Good slotting reduces travel time and is a common feature or add-on in WMS platforms.
- Statement of work (SOW)
- The contract document that defines an implementation partner's scope, deliverables, assumptions, roles and fees. Vague assumptions in the SOW are the most common source of change orders.
- Three-way match
- An accounts payable control that checks a supplier invoice against the purchase order and the goods receipt before payment is approved. Procure-to-pay software automates the match and routes exceptions.
- Total cost of ownership (TCO)
- The full cost of a system over a set period, usually three to five years, including subscriptions, implementation, integration, internal staff time, support and upgrades. Comparing vendors on TCO rather than license price alone often changes the ranking.
A
C
D
E
F
H
L
M
N
P
R
S
T