What order follow-up and export teams need to verify before shipment

Customer requirements, production candidates, actual completion, shipment readiness, and external transport events come from different owners. Order follow-up and export teams need to reconcile them around the same order while each milestone retains its own time, source, and version.

Primary readers
Manufacturing order follow-up, order coordination, export, and logistics liaison teams
Daily review
Customer milestones, production risk, shipment readiness, booking cut-offs, and actual events
Current boundary
Kavop starts with read-only APS review while responsible parties confirm external facts

Define the role boundary from the manufacturer's own structure

Manufacturers use different titles and reporting lines. Order follow-up, order coordination, export documentation, logistics liaison, sales, planning, warehouse, and customs work may be combined or split. Role names and authority need to be confirmed against the company's own division of work. This page does not prescribe an organization chart.

The daily job is to reconcile what the order promises, where production stands, what has actually finished, which readiness conditions remain open, whether booking or cut-offs changed, and who confirmed the latest fact. A shared view can bring those questions together while each owner remains accountable for the underlying record.

This page describes a role workflow and Kavop's long-term order-operations direction. APS production scheduling and due-date analysis remain the most mature externally validated product today. Order coordination and ocean-milestone connections require step-by-step verification.

Separate the customer request, candidate date, and authorized promise

When a customer asks for delivery by month-end, clarify whether that means factory shipment, port arrival, or customer receipt. Record the product, quantity, locations, time zone, split conditions, and acceptable date range. A date without a milestone can acquire three meanings across sales, planning, and export work.

The customer's requested date is an input. Production uses current supply, routings, resource calendars, and finite capacity to calculate a candidate. An authorized owner then decides which quantity and milestone the manufacturer can communicate. Each layer retains its own state, time, version, and owner.

A change to quantity, specification, routing, supply date, or customer milestone can require another review under the manufacturer's rules. A date that remains on screen does not establish that it remains feasible.

Use the production plan to test feasibility under current constraints

Planned completion comes from the current schedule. An order-follow-up review also needs the order version, routing, resource calendar, material state, data cutoff, and the labor, tooling, outside work, or shop-floor exceptions omitted from the current scope.

Finite-capacity scheduling can place the new demand beside existing orders and review precedence, reserved capacity, shifts, downtime, changeovers, and protected work. The result should show which orders may be late, where the bottleneck sits, and who a change affects instead of presenting one precise-looking completion date without its basis.

A planner still reviews the production candidate. Candidate schedules, business confirmation, vendor-specific firm or release actions, shop-floor execution, and customer commitments are separate actions with different terms and write-back effects across systems.

Verify shipment readiness after actual completion

A scheduled date does not turn into actual completion when the date arrives. Actual quantity and time need production feedback or another execution record, and partial completion remains separate from completion of the full order. Keep the source and update time so a planning value is not reused as a shop-floor fact.

Quality, post-processing, packing, labels, put-away, and warehouse handoff may remain after actual completion. The manufacturer defines shipment readiness for its product and service model, including quantity, quality state, packing and labels, handoff location, and confirmer.

Shipment readiness is an internal control point. It does not establish booking confirmation, gate-in, customs release, or vessel loading. Production, quality, warehouse, and export owners confirm the facts assigned to them.

Version booking confirmation and every cut-off separately

A booking request accepted for processing is not a confirmed booking. Preserve the request reference, carrier booking reference, confirmation version, amendment state, routing, and equipment separately, then recheck empty pickup, stuffing, and full-container return when they change.

Shipping Instructions (SI), Verified Gross Mass (VGM), Container Yard (CY) or Container Freight Station (CFS) delivery, earliest gate-in, and applicable filing milestones can carry different locations, time zones, and deadlines. Use the latest booking confirmation, formal notice, and local rule instead of relying on one permanent lead time.

Shipping Instructions provide input to the transport-document process, while VGM records verified gross mass for stowage. They are not the same record. VGM is a condition for loading, but it does not grant a right to loading or establish that loading occurred.

Keep filing, customs release, arrival reporting, and gate-in distinct

Goods declaration, manifest data, arrival reporting, customs release, and loading-manifest records have different parties, documents, and timing. China Customs guidance explains these distinctions for China. It does not replace another jurisdiction's rules.

Gate-in records entry into the relevant facility, while customs release records a regulatory status under the applicable process. The events may relate to each other, but neither proves the other or establishes vessel loading.

Each external value needs a source, time zone, update time, and owner. Carrier, forwarder, terminal, and competent-authority records continue to govern the facts within their responsibility.

Keep estimated and actual ocean events separate

ETD and ETA are estimates for events that have not occurred and can change with vessel, port, and connection plans. ATD and ATA record corresponding actual events and still need a location and event definition. None of them automatically equals the customer's delivery milestone.

Loading, actual departure, transshipment arrival, connection loading, and final arrival should remain separate. After rolled cargo, a vessel change, port omission, or routing change, recheck the next leg, final ETA, and customer communication version.

DCSA standards describe ways to exchange commercial schedules and transport events. The existence of a standard does not establish carrier adoption or prove that Kavop has integrated the interface or provides real-time tracking.

Recheck the order after every change and start read-only

A change to quantity, specification, planned completion, actual completion, quality state, equipment, booking route, or cut-off needs an affected-milestone review. Record the old value, new value, source, owner, and next review time, including whether a production change reaches a confirmed shipment arrangement.

A first round can fix one de-identified order set and one data cutoff, then reconcile customer requirements, the current schedule, actual completion, shipment readiness, booking confirmation, and external milestones. The review shows sources, differences, and open items for responsible owners to confirm before action.

Kavop does not currently automate quotation, order acceptance, delivery promises, booking, customs filing, SI or VGM submission, and it is not a provider of real-time ocean schedules, AIS data, container tracking, or freight forwarding. The first round makes no automatic production or logistics write-back, and current product validation remains centered on APS scheduling.

Common questions

Is order follow-up or export coordination one globally uniform role
No. Titles, reporting lines, and authority vary by manufacturer. This page organizes the order and shipment facts these teams often review, while actual responsibility follows the company's structure and local rules.
Does production completion mean the order is ready to ship
No. Actual quantity, quality, post-processing, packing, labels, put-away, and handoff conditions may still need review before a responsible owner confirms shipment readiness.
Does booking confirmation mean the cargo has loaded
No. Booking confirmation, cut-offs, gate-in, customs release, loading, and actual departure are distinct milestones, and later arrangements can still change.
Does Kavop already automate booking, customs, and real-time tracking
No. APS production scheduling and due-date analysis remain the mature product today. External milestones can be reconciled manually in a read-only review, while integrations and automation require separate verification.

Public sources

These sources distinguish order dates, production states, booking, documents, cut-offs, regulatory states, and ocean events. Vendor and standards materials support only their stated scope. They do not define a manufacturer's job structure, establish equivalent Kavop capabilities, or imply endorsement.

  1. Microsoft Learn Order promising
  2. Microsoft Learn Finite capacity planning and scheduling
  3. Microsoft Learn View, manage, and approve planned orders
  4. Microsoft Learn Production process overview
  5. SAP Advanced Available-to-Promise
  6. Oracle Availability Dates
  7. DCSA Booking technical implementation guidelines
  8. DCSA Bill of Lading 3.0 Introduction
  9. DCSA Cut-Off Time Code information model
  10. DCSA Shipping Glossary
  11. DCSA Track and Trace standard documentation
  12. DCSA Commercial Schedules
  13. IMO Verification of the gross mass of a packed container
  14. China Customs goods declaration guide
  15. China Customs manifest administration guide

Select one order set and reconcile production facts with shipment milestones.

The first round begins with a read-only APS review. Responsible owners confirm external milestones, with no automatic booking, filing, or write-back. Findings from one sample cannot be extrapolated to the whole plant. Order coordination and ocean shipment are Kavop's long-term direction around one order, not a complete production product flow already in market. Current public material does not establish completed Kavop product integration for ocean-shipment milestones; external events remain grounded in sources accepted by the manufacturer. The current scope does not automatically quote, accept orders, promise dates, book cargo, file customs, submit SI or VGM, or replace authorized logistics parties. File or snapshot intake does not establish real-time synchronization, bidirectional integration, conflict handling, or production-system write-back.

Book an order-milestone review