Know who received the lot.Connect the response and credit.
Connect purchase orders, received lots, and customer shipments so operations, customer service, and finance can act from the same product history.
Cost pressure. More buying relationships.More records to connect.
labor savings emerging as a critical factor alongside traditional concerns about integration and ROI.
One order can arrive in parts.One lot can leave on many orders.
Ordered, advised, and accepted tell different stories.
A supplier order can have several ASNs and lot allocations. Keep the accepted receipt and outstanding demand visible when a delivery is short, held, or incomplete.
Picks change the order’s shape.
Keep the source lot and recorded packaging relationship when quantities move from cases to packs, mixed pallets, or customer orders.
The response and the credit travel through different teams.
Connect each customer’s notice, acknowledgment, and action evidence to its commercial review, while supplier recovery keeps a separate approval.
Connect buying, receiving, and customer demand.Keep the lot through every allocation.
Bring supplier and customer order references together with shipment and receiving evidence from your connected systems, so each quantity keeps its source, unit, and state.
Follow partial supplier deliveries
See what the PO ordered, what each ASN covers, and what has been accepted at the DC.
Record the receiving exception
Compare advised and arrived quantities, then retain the accepted, held, or disputed result.
Retain the lot on customer orders
Connect each picked quantity to its source lot, shipment reference, and recorded case-pack relationship.
Open the work that needs attention
Follow current recorded stock, in-transit allocations, and unanswered receiving evidence from the selected DC.
Follow the customer’s response.Retain the basis for the credit.
Connect scoped supplier instructions and each customer action with the evidence operations and finance need to review the consequence.
Harbor’s response so far
Harbor’s acknowledgment is pending, and no customer notice is recorded yet. Delivered or read is not acknowledged, and acknowledged is not acted on.
Maintain the plan, contacts, and escalation route before the next supplier notice.
- Exercise
- Test only · MR-DW-READINESS-261012
- Plan
- RPL-DW-TEST-261012 · v1
- Participants
- 1 of 2 confirmed
- Open work
- ACT-DW-TEST-261012-01
- Owner
- Site response lead
- AI phone call
- No explicit acknowledgment
- Next
- Retry after 12:45 PM, then response coordinator
Credit and recovery basis
- Record set
- Recorded case · snapshot Oct 1, 2026 · 12:30 PM PT
- Customer credit requested
- None requested
- Shipped and invoiced basis
- 8 cases shipped; invoice not recorded
- Unit, rate, and currency
- Not recorded
- Requested and approved amount
- Not recorded
- Action evidence
- Not recorded
- Supplier recovery
- None requested; responsibility not assessed
One product history.Connect the work on both sides.
Follow the lot through the DC.
Track received and allocated quantities, then trace the recorded customer shipments and onward relationships.
Explore Track and TracePrepare and coordinate the response.
Maintain recall plans and exercises, then follow scoped notices, acknowledgments, customer actions, and escalation.
Explore RecallReview supplier and own-brand evidence.
Collect and scan the requirements for each supplier, product, and site, then track review, acceptance, and renewal.
Explore Supplier ComplianceValidate credits and supplier recovery.
Link claims to quantity and cost evidence, retain separate approvals and settlements, and eliminate identified fraudulent claims.
Explore Financial ReconciliationPrepare applicable FDA records.
Maintain traceability plans and generate sortable records for the requested scope, then share them directly with the FDA contact.
Explore FSMA 204Orders, product, and customer response.Find answers across your records.
Search purchase demand, lot allocations, customer response, supplier requirements, readiness, and financial review through their connected records.
Inspect inbound allocation. Harbor’s inbound receipt establishes eight cases available for the selected onward allocation.
Questions across the platform
Which Harbor customer shipments contain TLC-CAESAR-9941, and which receiving evidence is still pending?
Harbor received 8 cases on RCV-HBF-0930 and shipped them as 3 + 3 + 2 cases. Pacific Caterers and Bay Market have recorded receipts for 6 cases. Mesa Kitchen’s 2 cases are expected at 4:00 PM, so its receipt is not yet recorded at the 12:30 PM snapshot.
| Customer | Shipment | Cases | Receiving evidence |
|---|---|---|---|
| Pacific Caterers | ASN-HBF-9941-01 | 3 | Receipt confirmed · RCV-PCT-9941-01 |
| Bay Market | ASN-HBF-9941-02 | 3 (72 packs) | Receipt confirmed · RCV-BAY-9941-01 |
| Mesa Kitchen | ASN-HBF-9941-03 | 2 | Receipt not yet recorded · expected 4:00 PM |
Records: RCV-HBF-0930 · ALC-HBF-9941-01 · ASN-HBF-9941-01 · ASN-HBF-9941-02 · ASN-HBF-9941-03
Follow the lot through each customer branch.Connect the response and commercial review.
From the supplier receipt to customer allocations and separate receiving evidence, retain the records behind the response, credits, and recovery.
Receive the supplier lot
Recorded case · snapshot Oct 1, 2026 · 12:30 PM PTThe shipping notice says what left; Harbor’s own receipt says what arrived. The specification is a separate document with its own review state.
Freshfield’s notice meets Harbor’s receipt
- Shipping notice
- ASN-9941-03
- DC receipt
- RCV-HBF-0930
- Received
- 8 cases × 24 = 192 packs
- Specification
- SPEC-HBF-2026-001 v1 · not yet reviewed
- Product movement
- Document, request, or notice
- Instruction or acknowledgment
- Credit or recovery review
- Not recorded yet
Each customer branch retains its shipment and response history; credits and supplier recovery remain separate reviews.
Connect with the systems you already use.
ImpactRecall connects with the systems your teams already run, so you capture FSMA 204 records without replacing existing tools.
Map demand and sources.
Choose one DC, supplier lot, and customer orders.
Connect the records.
Bring ERP, WMS, EDI, or source files with their units and references.
Validate each branch.
Check allocation, shipment, and independent receiving evidence.
Exercise the response.
Work through one customer action and its credit or recovery basis.
Find your starting point.Six optional questions.
Answer what applies to your DC. The answers shape the first lot, branches, and records we look at together.