Customer orders and positions

A customer order groups demand into positions. A manufactured position can be fulfilled by one or several root production orders. Service and charge positions retain context without creating manufacturing work. Standalone production orders remain supported.

Create demand

Select the correct site/environment and open Orders → Customer orders. Reading, creating and editing customer demand have separate permissions; production linking/creation additionally needs the relevant production access.

1. Create a customer order and enter its order number. Customer name and customer reference are separate optional fields.
2. Enter header description and requested loading/delivery dates where agreed.
3. Add positions with position number, type, description, positive ordered quantity and unit.
4. Add product code, position dates and specifications where needed. Each specification needs a unique name.
5. Save, reopen and check every position against the agreed demand.

Keep units literal: one ordered pair or set remains one pair or set. Do not convert it into pieces without an explicit product/unit definition. Positions retain their identity even if display position numbers change.

You can also create demand from documents in Konnie. Every usable source order opens in the same customer-order drawer, including service-only orders and products without manufacturing mappings. Missing production setup stays separate from demand validation. Saving demand does not create or start production.

Plan production for a position

Open a manufactured position's production controls. Create a production order for the intended quantity, or link an existing root production order. Check product identity, matching units and the material routing before confirming. New operations remain unscheduled. Plan the final operation in the scheduler; the saved scheduling policy controls the preceding work. Component suborders stay under their manufacturing parent and cannot independently fulfil the position.

Several production orders can fulfil one position, for example two batches of 50 for demand of 100 pieces. Review the displayed ordered quantity, assigned/planned quantity, recorded production and quantities still to plan/produce. Over-assignment warns that linked production exceeds demand. Counts describe visible accessible records and cannot be summed across unlike units.

Mixed variants within one position

Keep a commercial position together when its quantity contains several variants. In Production allocations, enter each variant's name and quantity and select its existing production fields and values. For example, a position for 35 doors can contain 10 right-hand doors and 25 left-hand doors. The allocation quantities must add up to 35; pairs and sets keep their original units.

Choose a mapped material with a published routing. Shared position specifications apply to every allocation; allocation specifications override them for that variant. Release creates one production order per remaining allocation, with the matching routing operations. The position displays each linked order's variant. When creating a smaller batch, choose the saved allocation; later release creates only its remainder. Resolve unknown production fields before creating production. Allocations with linked production require reconciliation before they can be changed.

Release all remaining demand

For an open customer order not already released, choose its release action. The review lists open manufactured positions with unassigned quantity. Existing assignments are retained; services and charges do not create production orders.

1. Review each remaining position and quantity.
2. Confirm and inspect the newly linked production orders.
3. Plan the final operation in the scheduler. The saved scheduling policy controls the preceding work.

Production creation uses available published material routing and leaves its operations unscheduled. An ordinary position without a material routing receives an initial production step; configure its work center and timing before planning. Requested loading and delivery dates remain separate commercial targets. An explicitly documented dispatch or delivery week is stored as a week, never converted into an exact day. Existing linked orders keep their schedule.

Customer-order release creates linked planned production work; production lifecycle release and execution remain separate. See Planning for deadline and capacity rules.

Change or cancel demand

Edit the current customer-order revision. Changes to production-relevant positions with linked work can require explicit reconciliation rather than rewriting production. Review existing assignments before altering quantity, unit, product or specifications.

Removing a production link is limited to eligible unproduced planned/cancelled work. Deleting customer demand is blocked while production links remain. Cancelling a customer order does not cascade to production orders; review each affected production record separately.

Recovery

For a revision conflict, reload the current order, compare the saved change and reapply your intended edit. For duplicate order/source warnings, find the existing demand before creating another record. For a rejected link, check root/component identity, unit, material, cancellation and existing position assignment. If release reports “already released,” reload and inspect linked orders before retrying.

Structured source metadata identifies an import but does not authorize ERP writeback. Prices, invoices, shipping and Warehouse bookings are separate workflows. See Nexus for demand-to-production relationships and ERP and API integration for integration setup.

Material configuration

Configurable manufactured positions use the existing material and its published 150% BoM. Parameters define types, fixed units, bounds, precision and conditions. The same rules apply in the order editor, an App's Product Configurator and Konnie. No new material master is created for each position.

Konnie prepares the same customer-order drawer for all usable source positions. Configurable products use their published definitions; services, charges and products without a manufacturing mapping remain visible as demand. A source with no usable positions shows an explicit interpretation failure. Konnie prepares multiple editable configured positions directly in the conversation. Review each configuration, then create production for one ready position or all selected ready positions. This action saves the customer order and creates linked production using the accepted configurations. Services and charges stay on the order by default without manufacturing demand; the additional-position section lets you keep or exclude them. The separate order-only action records all valid reviewed demand without creating production. Products without the required manufacturing setup stay demand and report the missing setup when production is requested; no manual manufacturing fallback is invented. A request only for a customer order does not authorize production. Manual corrections are saved in the shared draft.

Accepted values and the configuration definition remain traceable on the position. Successful production and remaining issues are shown separately; uncertain results resume the same saved request. Creating production saves the customer order and creates planned production orders. Schedule them separately in Planning. While confirmation is pending, use Resume to check the same saved request rather than creating another one. A changed manufacturing definition needs renewed review; existing production is not silently changed. Konnie can perform the same production action after explicit user instruction under normal approval and autonomy settings. The positions-added event can trigger an explicitly configured Automation, which requires its own approved delegated permissions.