Book a demo

How one manufacturing order moves from customer inquiry to ocean shipment

Connect customer requirements, feasible-date review, finite-capacity scheduling, plan confirmation, actual completion, and externally sourced shipment milestones in one reviewable path. APS remains Kavop's mature product today. Order coordination and ocean shipment are a long-term direction.

Schedule one order setExplore APS scheduling
One order thread
Requested dates, candidates, execution facts, and shipment milestones retain distinct states
Current starting point
APS scheduling, due-date analysis, option comparison, and planner confirmation
Operating boundary
Read-only first round with no automatic order entry, promise, booking, customs action, or write-back

Keep one order on one reviewable thread

A manufacturing order may begin with an inquiry or a requested date, then move through order review, a feasible-date candidate, production scheduling, plan confirmation, actual completion, shipment readiness, and external transport milestones. A stable order reference links the thread while each milestone retains its own state, time, source, version, and owner.

This page describes the operating method and long-term product direction Kavop intends to pursue. It is not a list of modules already in production or a customer case. APS production scheduling and due-date analysis remain the most mature externally validated product today.

Order coordination and ocean milestones can be connected around the same order set as data, interfaces, and responsibilities are verified. A customer request does not become a promise by appearing in one view, and an external sailing does not become a Kavop-generated fact by being displayed.

Start order review from the customer's request

When a customer asks for delivery by month-end, sales first needs to clarify whether that means factory shipment, port arrival, or customer receipt. Record the product, quantity, locations, time zone, split conditions, and earliest or latest acceptable range.

An inquiry and requested date are review inputs. They do not establish a generated quote, accepted order, or delivery commitment. A fixed lead time can support an initial screen, while work requiring new production, critical material, or constrained resources needs supply and capacity review.

Order review also needs a data cutoff and input versions. A change to quantity, specification, routing, supply date, or requested milestone can invalidate the earlier conclusion, so retain old and new values before deciding whether to recalculate.

Produce evidence-based feasible-date candidates

A feasible-date candidate needs a quantity, calculation time, data scope, assumptions, and a defined ship or arrival milestone. Available and incoming supply may support an availability check. New production also requires material, routing, resource-calendar, and capacity review.

Microsoft, SAP, and Oracle use requested, confirmed, expected, scheduled, and promised in product-specific ways. This page uses three practical layers called the customer's requested date, a feasible candidate date, and an authorized commitment. It does not collapse vendor fields into one generic due date.

The candidate is one result under the current records and rules. Sales or another authorized owner still decides whether to communicate it, for which quantity and milestone, and retains the communication version. Software does not make an unconditional commitment for the manufacturer.

Place the order into a finite-capacity schedule

A new order needs more than an isolated theoretical slot. Review it with existing orders across operation precedence, critical machines, shifts, reserved load, materials, changeovers, downtime, and protected work to see which commitments may move.

Finite capacity covers only constraints configured and represented in the current scope. If labor, tooling, outside work, or a shop-floor exception is missing, the schedule will not infer it. Mark missing facts for review instead of hiding them behind defaults.

The same data cutoff can produce multiple candidates. Planners compare late orders, bottlenecks, affected work, and unresolved conditions before adjusting priorities, resources, or rules. Scenario comparison exposes trade-offs. It does not establish one uniquely correct or globally optimal answer.

Let the planner review, adjust, and confirm

A candidate schedule, planner confirmation, plan firming or release, and a date communicated to the customer are distinct actions. The business defines who can change a plan, approve an operating exception, make an external promise, and write which objects into ERP or MES.

Planners review candidate dates, operations, resources, materials, moved work, and omitted constraints order by order. An adjustment requires another impact check together with the old value, new value, editor, time, and reason.

Approved, firmed, and released refer to different objects and consequences across systems. This overview describes the control points a manufacturer needs without presenting one vendor's state model as a universal workflow.

Separate actual completion from shipment readiness

Planned completion comes from the current schedule. Actual completion needs production feedback or another execution record with actual quantity, time, and source. A date arriving does not convert a plan into an actual event, and partial reporting does not establish that the entire order is complete.

Quality, post-processing, packing, labels, put-away, and warehouse handoff may remain after actual completion. The manufacturer should define shipment readiness for the selected service model, including agreed quantity, applicable quality state, packing and labels, handoff location, and required source data.

Shipment readiness is an internal control point rather than a global standard. It does not establish booking confirmation, gate-in, customs release, or vessel loading. Production, quality, warehouse, and order-follow-up owners confirm the facts assigned to them.

Connect booking, cut-offs, and ocean events

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.

Shipment cut-offs are not one generic deadline. Empty pickup, earliest full-container return, CY or CFS delivery, Shipping Instructions, VGM, and applicable filing milestones can each carry a location, time zone, and version. Use the latest booking confirmation, formal notice, and local rule.

Gate-in, customs release, loading, estimated departure, actual departure, estimated arrival, and actual arrival are distinct events. ETD and ETA remain estimates, while ATD and ATA record corresponding actual events. Carrier, forwarder, terminal, and competent-authority sources continue to govern ocean, terminal, and customs facts.

Start with a read-only review of one order set

A first round can select one de-identified order set and fix a cutoff for ERP exports, spreadsheets, the current schedule, and operating rules. Preserve the current plan as the baseline, then create due-date and schedule candidates for order-level comparison.

Execution facts for completion, quality, and packing, together with booking confirmations and external milestones, can be reconciled manually from records held by their responsible owners. Each value retains its source and version so the team can see which production change may reach which shipment milestone.

Kavop does not currently automate quoting, order acceptance, customer 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 write-back to production or logistics systems. Planners and business owners review before acting.

Common questions

Is this entire order path already a complete Kavop product
Not yet. Order to shipment is Kavop's long-term direction and operating method. APS production scheduling and due-date analysis remain the mature product today, while order coordination and ocean milestones require step-by-step verification of data, interfaces, and responsibilities.
Does it replace ERP, MES, TMS, a forwarder, or a carrier system
No. Kavop currently sits in the production planning layer, while existing systems retain commercial and execution facts. Carrier, booking, terminal, and customs states remain governed by their authoritative sources.
What records are needed for a first round
Start with one de-identified order set, requested milestones, routings, resources and calendars, critical materials, the current schedule, planned and actual completion states, the shipment records in scope, and one data cutoff.
Will the system automatically promise, book, or write back
Not in the first round. Kavop creates comparable production candidates for planner and authorized-owner review. Booking, filings, and external operations remain with their responsible parties, with no automatic production or logistics write-back.

Public sources

These sources distinguish order dates, finite capacity, planning controls, production states, booking, cut-offs, and external transport events. Third-party capabilities do not establish equivalent Kavop implementation, and inclusion does not imply endorsement.

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

Start with one order set and reconcile requested dates, production plans, and shipment milestones.

The first round begins with a read-only APS review and makes no automatic promise, booking, or system write-back. The first round stays read-only. 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. Current material must not present sample validation as a customer case, customer outcome, fixed ROI, industry result, or scaled deployment.

Book an order scheduling review