How to Ship a Customer Order in SyteLine (Partial and Backorder)
how to ship a customer order in SyteLine partial shipment backorder
Also searched as
- SyteLine order shipping form
- SyteLine ship partial quantity customer order
- SyteLine pick list and packing slip
- SyteLine shipped quantity cannot exceed order
Short answer
Shipping in SyteLine records the quantity leaving each customer order line, relieves inventory and creates the shipment that invoicing later bills. Enter a smaller quantity than ordered for a partial ship, and the rest stays open as a backorder on the line. Shipment, not the order, drives the invoice.
Applies to: Infor SyteLine 8.x and CloudSuite Industrial 9.x and 10.x. Form names and the use of picking vary by configuration.
How to ship a customer order
- 1Confirm the customer order is Ordered status, not Planned, and that there is no credit hold on the customer or order. A hold blocks shipping.
- 2Check availability for each line on the Item Availability or on-hand view for the ship-from warehouse and location.
- 3If your site uses pick lists, print and confirm the pick list so the stock is allocated and picked before shipping.
- 4Open the order shipping form, enter the customer order number and the lines to ship, then enter Qty to Ship per line. Enter less than the ordered quantity for a partial ship.
- 5Enter lot or serial numbers for tracked items, and the ship-from warehouse and location if they differ from defaults.
- 6Process the shipment so inventory is relieved and the shipment record is created. Print the packing slip.
- 7Check the order line: Qty Shipped has increased and the open balance remains as a backorder (Qty Ordered minus Qty Shipped).
- 8Run the invoicing process for the shipped lines, or let the scheduled invoice run pick them up.
What shipping actually changes
Processing a shipment writes the shipped quantity to the order line, creates a shipment record against that order, relieves the inventory with a transaction, and, depending on configuration, queues the sale for invoicing and posts cost of goods sold. The order line is not closed until it is fully shipped, or you manually close it short.
A partial shipment leaves the line open with the remaining quantity as backorder. MRP and the availability checks continue to see that remainder as demand, so it will be planned. If the customer no longer wants the balance, change the ordered quantity on the line or close it, rather than leaving a phantom backorder to distort planning.
Common shipping blockers
Credit hold is the most frequent: a customer or order on hold cannot ship, and the release is covered in the credit hold page. Next is stock: if on hand in the chosen location is below Qty to Ship, the system either refuses or lets inventory go negative depending on the negative inventory option on the item or parameters. Know which your site allows.
Other blockers include a line still at Planned status, a required lot or serial number not yet entered, a ship-to or tax code missing for the customer, and lines that belong to a different ship-from site. For drop-ship lines the flow is through the purchase order, not a warehouse shipment.
Shipping before invoice and fixing mistakes
Shipments are normally invoiced afterwards, in a batch or per order, and the invoice picks up what has shipped and not yet been billed. If a shipment was wrong and has not been invoiced, use the shipment correction or the unship function available on your release, then re-enter it. Once invoiced, you need a credit memo or a return process, not a delete.
For reporting on what shipped but is not invoiced, query the shipment tables for lines without an invoice reference. This list is a useful month-end control, since uninvoiced shipments are revenue you have delivered but not billed.
-- Shipped but not yet invoiced (verify column names on your release) SELECT cs.co_num, cs.co_line, cs.qty_shipped, cs.ship_date FROM co_ship cs WHERE cs.qty_shipped > 0 AND cs.inv_num IS NULL ORDER BY cs.ship_date;
Common pitfalls
- !Trying to ship while the customer is on credit hold, then assuming the shipping form is broken.
- !Leaving the balance of a partial ship open as a backorder when the customer cancelled it, which keeps creating planned supply.
- !Shipping tracked items without lot or serial numbers, or with the wrong location, causing inventory mismatches at cycle count.
- !Deleting a shipment after invoicing instead of issuing a credit memo.
- !Assuming a Planned status line can ship. It must be moved to Ordered first.
How an ERP-grounded AI assistant handles this
ERPray can answer shipping questions across live data, such as which order lines are past ship date, which are blocked by credit hold, or which shipments have not been invoiced, and it shows the query it ran. It never ships, unships or invoices on its own; write-back needs human approval. For one order, the standard shipping form and order view are faster than any chat tool.
Frequently asked questions
How do I ship part of a customer order line?
On the order shipping form enter a Qty to Ship smaller than the ordered quantity. After processing, the line shows the shipped quantity and the remainder stays open as a backorder until you ship it or close the line short.
Why can I not ship my order?
Check credit hold first, then order status (it must be Ordered), then available stock in the chosen location, then required lot or serial numbers. Missing ship-to or tax setup can also block it.
Does shipping create the invoice?
Shipping creates the shipment record and relieves inventory. Invoicing is a separate step run per order or in batch, which bills what has shipped and not yet been invoiced. Some sites schedule it automatically.
Can I reverse a shipment?
Before invoicing, use the unship or shipment correction function if your release provides it and re-enter. After invoicing, use a credit memo or return flow so the audit trail and revenue remain correct.
Related
SyteLine Customer Order to Invoice: Step by Step
A SyteLine customer order flows from Order Entry through pick, pack, and Customer Shipment, then to invoicing, either through the Auto Invoice batch utility or manual Invoice Entry, posting revenue and relieving inventory once the shipment is confirmed.
How-toHow to Release a Customer Order from Credit Hold in SyteLine
A customer order goes on credit hold when the customer's exposure, whether AR balance, open order value, or days past due, exceeds the limit set on the Customers form. Releasing it is a deliberate override on the order, usually restricted to users with credit management authority, and the real fix is reviewing whether the limit, the hold reason, or the customer's payment behavior needs attention.
How-toHow to Set Up Lot and Serial Number Tracking in SyteLine
Lot and serial tracking is turned on per item on the Items form, with a tracking type of None, Lot, or Serial. Once enabled, every receipt, job move, and shipment transaction for that item prompts for a lot or serial number assignment, and SyteLine keeps a full genealogy you can trace forward to customer shipments or backward to the receiving vendor.
How-toHow to Run a Cycle Count in SyteLine
Cycle counting in SyteLine runs through Inventory > Cycle Count: generate a count list by ABC class or location, print or enter tags, key the counted quantities into Cycle Count Entry, then review the variance report before posting the count to update on-hand quantity.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
AI for ERPAI on Infor SyteLine for Industrial Machinery Makers: Configured Orders, Projects and Service Parts
AI on Infor SyteLine for industrial machinery manufacturers: configure-to-order BOMs, project cost, spare parts and warranty, private and read-only by default.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.