You're reading the public documentation. Links to screens inside PrintERP will ask you to sign in first.

Packing, dispatching and delivering

The delivery lifecycle that opens automatically when a customer job is completed.

When a job with a customer is marked done, PrintERP opens a delivery for it automatically. You never create one by hand — if a delivery is missing, the job either has no customer or is not finished yet.

The four stages

StageMeansRecorded
PendingFinished, not yet packedOpened automatically
PackedBoxed and ready to goTime packed
DispatchedLeft the buildingTime dispatched, courier reference
DeliveredWith the customerTime delivered

The order is strict — you cannot dispatch something that was never packed. Each step stamps its own timestamp, giving you a defensible record of when the goods left and when they arrived.

The courier reference

Dispatching lets you record a courier reference — a tracking number, a rider's name, “collected by customer”. It is free text, and it is the first thing anyone asks for when a customer calls about a late order.

Marking delivered also closes the job

Setting a delivery to Delivered moves its production job to Delivered in the same step, so the two can never disagree about whether the customer has the work.

Finding deliveries

Deliveries lists them all with a status filter — Pending is your outstanding pile. There is no sidebar entry: deliveries are reached from the production flow, and anyone with access to Production can open them.

A counter job has no delivery.

Correct. Walk-in jobs have no customer to deliver to, so they finish at Completed.

The customer collected it themselves.

Pack it, dispatch it with a reference such as “collected in store”, then mark it delivered. The trail stays complete.

It was returned.

There is no return stage. Record what happened in the notes and handle any reprint as a new job.

Open Deliveries

Open →