Logistics scenarios

How Controlled Sales Core fits into standard Business Central logistics setups for sales, transfer, and transport flows.

Purpose

This page explains which standard Business Central logistics variants are available and how Controlled Sales Core fits into the operational flow. The key question is simple: Which action belongs to which location setup and document type?

Core Principle

In Business Central, the location setup determines whether a document can be posted directly or whether shipment and/or pick documents must be created first. Controlled Sales Core sits exactly at that decision point: it filters the relevant lines, creates the necessary follow-up documents, and keeps the operational selection transparent.

Common Variants

Process 1) Sales without warehouse requirements Direct posting without dispatch control or warehouse documents.

The location does not require shipment or picking.
The sales order can be posted directly in standard BC.
Controlled Sales Core is only needed if later special processes must be documented.
This is the simplest variant and fits locations with no operational warehouse steering.

Process 2) Sales with shipment requirement Creates a shipment step before final posting.

The location requires shipment but not necessarily picking.
In Controlled Sales Core, dispatch control opens a worklist of shippable sales lines.
The Create Document action creates a warehouse shipment or prepares the posting step.
The normal BC shipment posting follows afterwards.
This variant fits locations with a clear shipment release step but no additional pick layer.

Process 3) Sales with picking requirement Creates a pick list before the actual shipment posting.

The location requires picking, but no classic shipment staging.
Dispatch control highlights the lines that belong to the pick process.
Create Pick or Create Warehouse Shipments with Pick creates the operational pick workload.
Shipment posting happens only after picking is completed.
This fits warehouses that separate material release and picking from shipment posting.

Process 4) Sales with shipment and pick Two-step warehouse handling with shipment document and pick.

The location requires both shipment and pick documents.
Controlled Sales Core supports creating both steps together from dispatch control.
In practice, shipment lines are created, released, and then pick documents are generated.
This is the most realistic option for tightly controlled warehouse operations.

Process 5) Transfer without warehouse requirements Direct transfer posting without additional warehouse steps.

The transfer runs without additional warehouse obligations.
Standard BC transfer posting is sufficient in that case.
Controlled Sales Core is only needed if shipment or transport details must also be captured.

Process 6) Transfer with shipment requirement Dispatch control for transfer orders with a warehouse staging step.

The location requires shipment for transfers.
Transfer Control filters the relevant transfer lines by due date and available inventory.
Create Whse. Shipment creates the outbound transfer shipment.
Standard transfer posting follows afterwards.

Process 7) Transfer with shipment and pick Complete transfer handling with shipment and pick steps.

This scenario combines transfer order, warehouse shipment, and pick.
Controlled Sales Core provides Create Whse. Shipment and Pick and Create Whse. Pick for that flow.
It fits locations with strong operational control and strict inventory protection.
The transport page can then document the posted shipment flow.

Process 8) Consignment as BC standard extension Combine sales-side execution with transfer-oriented replenishment and analytics.

The base remains standard location behavior with the Consignment option enabled on the Location Card.
Operationally, sales-side dispatch remains leading for shipment and picking execution.
For replenishment, a transfer-oriented downstream step can be derived from stockkeeping data.
In transport reporting, consignment is handled as Transfer from a business perspective.

Role of transports

A transport consolidates posted shipment data into one handoff to a carrier or internal logistics process.
Sales normally create transport lines from posted sales shipments.
Transfers create transport lines from posted transfer shipments.
At consignment locations, the process type can still be treated as transfer even when the source is a sales shipment.

Decision table for actions

Scenario	Typical CSC action	Result
Sales with shipment requirement	`Create Document`	Shipment document is created or prepared.
Sales with shipment and pick	`Create Document And Pick`	Shipment and pick are prepared in one run.
Sales in pick-oriented setup	`Create Pick`	Warehouse pick document is created.
Transfer with shipment requirement	`Create Whse. Shipment`	Outbound transfer shipment is created.
Transfer with shipment and pick	`Create Whse. Shipment and Pick`	Transfer shipment and pick are prepared together.
Extend an existing shipment	`Add to Whse. Shipment`	Selected lines are added to an existing shipment.
Final posting step	`Post Document`	Shipment/transfer posting is executed.

Decision table for process chains

Start point	CSC follow-up	Next step
Delivery call-off released	Sales lines are updated or created	Start dispatch control
Shipment posted	Transport is created from posted shipment data	Validate and post transport
Consignment location active	Transport process type is handled as `Transfer`	Analyze in transfer-oriented reporting
Consignment extension active	Sales and transfer logic are combined	Keep replenishment and transport typing consistent

Result

You can classify the appropriate BC standard setup for each location faster.
You see when Controlled Sales Core only filters lines and when it creates extra documents.
You understand the difference between sales, transfer, and transport flows more clearly.
You can classify consignment as a targeted BC standard extension with clear process impact.