Goods Receiving Workflow

How is this workflow audited?

Every step, from delivery record creation through inspection, status changes, and final routing decision, is timestamped and logged within assess.one. This creates a complete, exportable audit trail covering who performed each action, when the goods receipt or discrepancy record was created, and how the final outcome was reached, supporting internal audit and supplier dispute resolution requirements.

Who has access to the goods receiving workflow?

Access is role-based and configured directly within assess.one, typically granting warehouse receivers permission to log deliveries and inspections, while buyers and procurement staff receive read access and outcome notifications. Administrators can extend or restrict access at any step, including approval and discrepancy-handling stages, to align with organisational segregation-of-duties policies.

How does this integrate with existing procurement or ERP systems?

Integrations such as email or Slack notifications to buyers are configured inside assess.one, requiring no external development work. Purchase or shipment references entered at the delivery logging stage can be aligned with identifiers used in existing procurement systems, ensuring the goods receipt record remains traceable back to source purchase orders.

Can the inspection criteria or routing logic be customised?

Yes, the inspection step, acceptance thresholds, and routing logic between acceptance and quarantine are fully configurable within assess.one's no-code editor. Organisations can adjust which fields are mandatory, add additional approval gates, or introduce further branching for specific goods categories without any code changes.

What happens at the inspection outcome decision point?

Following inspection, the workflow automatically routes goods down one of two paths based on the recorded outcome. Goods confirmed free of damage or shortage proceed to acceptance, goods receipt creation, and putaway, while goods flagged with issues are quarantined and a supplier discrepancy is raised for follow-up, with the buyer notified in either case.

How long does implementation take?

This is a ready-to-use template that can be published in minutes. Once live, the warehouse team can begin logging deliveries and running inspections immediately, with no separate implementation project required.

What compliance or approval considerations apply to discrepancy handling?

When goods are quarantined, the workflow requires a discrepancy record and supplier follow-up assignment before resolution can be persisted, ensuring no discrepancy is closed without documented action. This structure supports internal control requirements around goods-not-as-ordered scenarios and provides an evidentiary record for supplier performance reviews.

Who needs to be notified when goods are accepted or quarantined?

Buyers are automatically notified at both final outcomes, whether goods are accepted and put away or quarantined with a discrepancy raised. Notification recipients and channels, such as email or Slack, are configured within assess.one and can be extended to include procurement managers or other stakeholders as required.

Can putaway locations and goods receipt data be tracked over time?

Yes, putaway locations are persisted as a distinct field within the workflow record, alongside the goods receipt itself, enabling historical reporting on storage patterns and inventory placement. This data remains accessible for audit, reconciliation, and warehouse optimisation purposes.