AID gives your operation its own searchable record of what physically arrived, when it arrived, and where it entered your facility—even when no ERP receiving record is created.
Carrier portals tell you what the carrier believes happened to a shipment. AID records what your facility actually observed at the point of receipt.
Useful—but it reflects the carrier’s delivery event.
Your timestamp. Your station. Your searchable receiving evidence.
AID gives receiving teams an internal record to compare against UPS, FedEx, USPS, Amazon, and other delivery confirmations when a parcel is missing, disputed, or difficult to trace.
AID provides the internal arrival record for carrier audits. Automated carrier-portal reconciliation is not part of the current product.
AID works whether physical arrival is eventually received in an ERP or never gets an ERP record at all.
Capture indirect material, non-inventory purchases, no-PO orders, engineering samples and supplies when no formal ERP receiving record is created.
Keep your normal ERP process while capturing the physical-arrival event your system may not record until later.
Use the AID timestamp as the start point, then compare it with inspection-complete or release timestamps from your quality process.
It does not need to replace carrier tracking, your ERP, or your quality system. It gives each of them a reliable physical-arrival anchor.
The carrier reports that the shipment reached the destination.
Your team scans the parcel and creates the internal receiving record.
The business transaction posts later—or not at all in non-ERP workflows.
Material clears the next operational step.
AID stays intentionally narrow: fast receipt capture, searchable evidence, and a clean operational history.
Log a parcel in seconds without navigating a transaction-heavy ERP screen.
Give every arrival a permanent internal reference that remains part of the record even when voided.
Answer questions by tracking identifier or Arrival ID instead of searching paper, inboxes, or carrier portals.
Correct classifications and preserve the receiving record rather than silently rewriting history.
Start a 14-day free trial with a scanner, one receiving station, and up to three named users. Create your internal arrival record before deciding whether to subscribe.
Then $199/month if you choose to subscribe. No onboarding fee. Your trial does not automatically charge you.
Create an organization to start a 14-day trial. The trial does not automatically convert to a paid subscription. If AID fits, you can choose the $199/month plan separately; no onboarding fee applies.
Carrier tracking records the carrier’s delivery event. AID records your facility’s receiving event. That gives you an independent internal record when delivery status and physical reality do not line up.
Yes. AID provides a scanner-based arrival ledger for indirect, non-inventory and other deliveries that do not create an ERP receipt.
AID can sit alongside it. The AID timestamp represents physical arrival; your ERP receipt represents the business-system transaction. Comparing those events can expose receiving backlog or delay.
AID provides the physical-arrival timestamp—the start of that clock. To calculate full dwell time, you also need the downstream inspection-complete or release timestamp from your existing process or a future AID workflow.
No. AID gives you an internal receiving record to compare with a carrier delivery confirmation. Automated carrier reconciliation is not included.
No. AID is intentionally focused on receiving control and physical-arrival evidence. It can be a primary parcel receiving log or an independent event layer alongside ERP/WMS processes.
AID stores an organization-wide shared arrival history. The current plan may limit active stations; verify the plan before adding one.