Field notes on tracking, inventory and rollouts
Practical, long-form guides for the people who run receiving docks, count stock, chase shipments and put new systems live.
Scope a project
ERP or WMS: which system should own each inventory number?
Why read it: Most ERP vs WMS pages compare products; this one assigns an owner to every inventory number, from bin on-hand to valuation, and shows the sync and daily reconciliation that keep the two records in step.
ERP vs WMS for inventory data: a field-by-field ownership matrix, sync patterns, 3PL 944 and 947 flows and a daily reconciliation routine you can run.
Read the field note
25 field notes in five sections. Issue dates show the editorial calendar month each note belongs to.
Inventory accuracy and control
Counting, locating and adjusting stock so the number in the system is the number on the shelf. Open the inventory control section
Shipment tracking and visibility
Milestones, carrier events and exceptions, from purchase order to proof of delivery. Open the shipment visibility section
Barcodes, standards and traceability
GS1 identifiers, labels, RFID and the record-keeping rules that ride on them. Open the traceability and standards section
Integrations and data
EDI, APIs and master data between ERP, WMS, TMS and trading partners. Open the integrations section
Requirements, rollout and onboarding
Requirements, plans, testing, cutover, documentation and training. Open the implementation section
How the field notes work
Each field note answers one question that comes up when a team is fixing a count, chasing a shipment, meeting a trading partner’s label rule or putting a new system live. They are long because the questions are: a definition and a formula fit on a card, but the decisions around them do not.
Every note follows the same rules:
- One reader question, stated at the top, and answered in the first section before the detail starts.
- Primary sources, linked where they are used: regulations, standards bodies, carrier service guides and the ASCM dictionary rather than summaries of summaries.
- Worked examples that are labeled as fictional. The numbers in an example are there to show the arithmetic and the decision, not to describe a real company.
- One visual near the passage it explains, such as a decision table, a timeline or a chart, with a caption that says where its numbers come from.
Issue dates and publication dates
Field notes are organized into a twelve-month editorial calendar. The issue date on each card and article is the calendar month the note belongs to. The published date on the article is the day it actually went live on this site, and an updated date appears only when the content changes in substance. The editorial calendar is a way of ordering the library; it does not describe when GenFrontier began operating.
Use them with the tools
Many notes pair with a working tool: the safety stock calculator, the freight density calculator, the tracking milestone map or the FSMA 204 KDE worksheet. The notes explain the judgment; the tools do the arithmetic.
Read how the editorial team writes and checks field notes, or, if a note describes a problem you need solved, scope a project.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.