Review and confirm a delivery order

Reading the split view

The header reads Confirm delivery order fields with the container number beside it. Below it, the source PDF fills the left pane and the review rail fills a fixed column on the right. On a phone the two panes collapse into a toggle labeled Document and Fields; the screen opens on Fields, because that is where the work is.

Each row in the rail has the same shape: a label, the control you actually commit, and underneath it a muted evidence line reading Document: followed by what the parser pulled off the page. When nothing was found the line reads No document value found. Click that evidence line and the left pane highlights the matching text in the PDF, which is the fastest way to check a number without reading the whole page.

How the rail is grouped

Fields are grouped into Parties, Pickup, Moved By, Shipment, and Support Details, preceded by an unlabeled block holding the document date and issuer, and a Billing customer defaults section with Freight Customer and Accessorial Customer.

The required assignments

Text fields hold what the document said. Assignments are different: they bind the document to a real record in your workspace, and eight of them must resolve before Confirm will fire. Each one blocks with its own message.

Issuer

“Issuer must be selected or marked as not shown before confirming.”

Pickup terminal

“Pickup terminal must be selected before confirming.”

Vessel

“Vessel must be selected before confirming.”

Ocean carrier

“Ocean carrier must be selected before confirming.”

Container SSL

“Container SSL must be resolved before confirming.”

Local carrier

“Local carrier must be selected before confirming.”

Importer (BCO)

“Importer (BCO) must be selected or marked as not shown before confirming.”

Deliver To

“Deliver To must be selected before confirming.”

Broker and Freight forwarder are optional and never block a confirm. Deliver To location is conditionally required — see the next section.

Reading the state of a picker

1. Needs match. The parser read a name off the document but no canonical record is selected yet. The helper text says “Parsed from the document, but no canonical match is selected yet.” Focusing the field opens the picker for you.
2. An amber warning. Several active company records match the parsed name: “Multiple active company records match this parsed name. Resolve it to the canonical record.” Pick the canonical one rather than whichever sorts first.
3. Auto-filled or Manual. A resolved field shows where its value came from — a suggestion from the document, a value derived from the vessel, the container BIC or the B/L prefix, a workspace default, or your own search. Auto-filled is not the same as verified; check it against the evidence line.

Resolving Deliver To: company, then site

Every delivery stop uses the same card. Choose the company first. If the delivery is handled through another company, choose that optional Care Of company next. Then choose a saved delivery site owned by either company. If the address is new, the card keeps the address fields and states that the address will be added to the Deliver To company when you confirm.

1. Pick the company. An unresolved Deliver To carries the label Needs owner. If the parsed name matched nothing, the helper reads “No existing Deliver To company matches this document yet. Create it or choose an existing org instead.” If several companies matched, you get “Multiple existing companies could match this Deliver To. Pick the right one before choosing a site.” and a Choose the matching Deliver To company list where each candidate has a Use action.
2. Add Care Of only when needed. Care Of is optional and does not replace Deliver To. Use it when another company receives or handles the load for the Deliver To customer. The POD prints that company as C/O directly below Deliver To.
3. Choose the destination. For a saved destination, use the delivery-site picker. After you select Care Of, the picker includes active saved sites owned by either Deliver To or Care Of. For a new address, keep the street and city/state/ZIP shown in the card. The card does not ask for a second site name.
4. Resolve an unclear site. The picker labels itself Choose or create site and tells you which case you are in: “Similar saved site found. Choose it or create a new site.” or “Multiple saved sites could match. Choose one or create a new site.” When nothing matches a valid parsed address, the new site is staged automatically for Confirm.

The warehouse case is the two-level one people trip on: a warehouse company can own many yards and docks, and the delivery address on the document identifies the site, not the company. Conterminal treats the company as the owner and the address as a saved site beneath it, so a second delivery order to the same warehouse at a different address is a new site under the same company — not a second company.

Adding more delivery stops

In Full Review, select Add stop for each destination. Every stop can select or add a Deliver To company, an optional Care Of company, and a delivery site. Use the arrows to move any destination, including into Stop 1. The stop in the first position is the scheduling destination. The route summary updates immediately, and the empty return stays last.

Existing company and site

Choose an existing Deliver To company, then a saved delivery site beneath it. Confirmation reloads the active company and site before it commits, so a renamed or retired record cannot leave a stale route snapshot.

New company or site

Use Add as Importer / BCO or Add as Warehouse in any stop's company picker. Enter an unsaved site's address in the same stop. Conterminal resolves or creates the site when you confirm, so the draft can move without losing its company or contact details.

Confirm stores each destination as its own delivery leg between the first delivery and the return. If dispatch work, assignments, or execution history already exists on the operation route, Conterminal refuses the rewrite instead of replacing live work.

Enter Goods and Pieces on each stop to allocate the load across destinations. Conterminal keeps that cargo with the stop when you reorder the route and prints it on that stop's POD. On a one-stop order, the original order-level cargo remains the fallback.

Open Optional stop details on any card to add a contact, phone, email, requested service date, requested time window, or delivery instructions. Those details move with the stop when you reorder the route and appear on its operation leg.

Creating a new company or site inline, and when a reason is required

You do not have to leave the screen to add a missing record. Every stop offers the same two company actions and can stage a delivery site for creation when you confirm.

A new company

Type the missing name in any Deliver To company picker, then chooseAdd as Importer / BCO or Add as Warehouse. Conterminal saves and selects the company on that stop. To use another saved company instead, keep typing in the same picker and choose its result.

A new site

Choose the company, then enter the street and city/state/ZIP. When no saved site matches, the card states that the address will be added to the selected company when you confirm. Exact matches are reused. Contact and service details stay collapsed underOptional stop details until you need them.

The other role pickers use the same creation seam. The shipment Importer (BCO) picker, for example, carries a Create new importer (BCO) action that uses whatever you typed as the name.

Confirming

Lookup results can include vessel, ocean carrier, pickup terminal, voyage, container size and type, B/L, and ETA. Every candidate names its provider, whether the evidence came from a terminal or SSL, and when it was observed. Nothing is applied automatically. Choose Use tracking or Keep current for an individual result. Use N blank fields is available only for blank fields with exactly one canonical result; conflicts and values that still need a canonical match stay for manual review. The panel also names every field the lookup did not find.

The Tracking evidence panel shows the ready vessel, voyage, pickup terminal, Last Free Day, source, and freshness. All document-versus-tracking decisions appear in the same expanded review section, and required differences still need an explicit choice before Confirm.

The primary button reads Confirm DO normally, and Confirm & Continue when you came in from the review queue. On a multi-container document the action first reads Save container. Use it after checking the active container's pieces, weights, seal, PO, and other container-specific values. Conterminal advances through the selected containers; after all of them are saved, the action reads Confirm N orders. A batch confirm is all-or-nothing: if any selected order fails, none are confirmed.

1. Watch the action bar. While fields are outstanding it summarizes them as, for example, “3 fields need attention.”
2. Press Save container or Confirm. If anything is unresolved the screen does not submit; it shows a red banner reading “Fix 3 fields before confirming.” listing up to five issues. Each listed issue is a button that scrolls to and focuses the field.
3. Fix and press Confirm again. The server re-validates independently, so a value that drifted since the page loaded is caught here rather than committed.

Find from tracking, Check again, and the batch grid's Refresh enrichment action follow the exact LongShorty work item they start. When that work finishes, Conterminal loads the materialized tracking candidates into the same review panel. If you reload while the work is still running, the page resumes that exact refresh instead of starting a second one. The server still binds Confirm to the exact ready review shown on screen; if that review was replaced or is no longer ready, the stale submission is refused so you can review the current evidence instead.

Where you land afterwards depends on what is left to do: the proof of delivery stage if it is available, then the confirmation email stage, then the next delivery order from the same document, then the next item in your review queue, and finally the order's detail page.

The POD stage

The proof-of-delivery stage replaces the PDF pane with the POD document itself, while the right rail switches to a read-only Confirmed DO summary — document date, issuer, container, BOL, broker reference, ETA — plus the delivery address and the route legs. When a stop has Care Of, the POD prints aC/O row directly below its Deliver To customer. The confirmed values stay in view while you print and reply.

1. Check the sheet. The desktop preview shows a letter page with two identical copies of the POD stacked on it — one for the driver, one for the file.
2. Select Print POD. After confirming several containers from one source document, the action reads Print N PODs and loads one merged PDF for that confirmed set. Conterminal opens a new tab that reads “Opening POD PDF...” and then loads the generated PDF.
3. Select Finish to leave, or Email Update to move to the email stage. Both are also in the Actions menu, along with Open source document and Open operations detail.

After confirmation, each delivery leg has its own POD controls in the shipment route. Print, upload, email routing, and Electronic POD actions target that exact stop, and the printed Goods and Pieces come from that stop. When an order has several stops, the print action becomes Print N PODs and generates one POD per stop. A POD on an earlier stop records its receipt without marking the order delivered; the final active delivery stop controls the delivered milestone.

The confirmation-email stage: draft, send, or skip

This stage only exists when the document arrived as an email attachment — there has to be a thread to reply to. If there is no draft, the email stage is unavailable and asking for it sends you back to POD.

The compose is a reply-all against the reconstructed thread: From, To and Cc as removable recipient chips, Subject, and a rich text Message. Typing pauses briefly and the draft saves itself; you will see Saving draft… in the toolbar while it does. Recipients are validated as you add them — anything that is not an email address is dropped rather than rejected loudly.

1. Review the recipients. If the thread reconstruction was uncertain the stage says “Review recipients before sending.” Sending with an empty To list is refused with “Add at least one recipient before sending.”
2. Send or skip. Send is the primary button; Skip sits beside it and is also available as Skip email in the Actions menu. Both close out the stage and move you along.
3. Check the history. The right rail lists Emails for this document with each message's kind, status, timestamp, and recipients, or “Nothing has been emailed for this document yet.” Sent and failed messages each carry a Resend button.

An already-sent email opens read-only with a green summary — “This confirmation email was already sent.”, or “The received confirmation was already sent.” when it was the automatic acknowledgment — and the buttons change to Back to POD and Continue to Next DO or Finish. A failed send exposes a Delivery diagnostics disclosure with the provider response.

Archiving instead of confirming

Some uploads should not be confirmed at all — a duplicate, a scan of the wrong document, a PDF that turned out to be unrelated. Open the Actions menu and choose Archive document. The item shows Archiving... while it runs, then returns you to the next item in the queue, or to the order's detail page if you were not in queue mode.

Archiving is only offered while the upload is still pending review. Attempting it later is refused in plain terms: “Confirmed DO uploads cannot be archived from this review screen.”, “This DO upload has already been superseded.”, or “This document has already been archived.”

Troubleshooting