Overview
A purchase order type (PO type) is a set of receiving rules. Every PO has a type, and Logiwa IO applies that type’s rules wherever the PO is received: on the web, on mobile and through the Open API.
For example, one PO type can let receivers take more than the ordered quantity, while another requires the lot number on the PO line to match what’s scanned. You choose the type when you create or edit a PO.
When to use it
You need different receiving rules for different vendors, clients or inbound flows, such as returns or cross-dock.
You want to enforce lot, expiry, production date or pack type matching during receiving.
You want mobile receiving to pre-fill attributes, require photos or count units one by one.
Prerequisites
Your role has access to Data Setup.
Step-by-step
Go to Settings > Data Setup and select Purchase Order Type in the left sidebar.
Click Create New PO Type. A type named Purchase Order is included as a system default.
Enter the PO Type Name and set the parameters described below.
Click Save. A confirmation message appears.
The new type appears in the Purchase Order Type list and in the PO Type field when you create or edit a PO. Parameters apply only to POs of this type.
PO type parameters
Parameter | What it does | Example |
PO Type Name* | Name shown in the PO Type field of a PO | Returns |
Allow Exceed Quantity | Lets receivers receive more than the ordered quantity on a line. Together with Allow Update When Started, it also lets them receive SKUs that aren’t on the PO | Line of 100 units, 105 received |
Warn When Quantity Exceeds | Shows a warning before an over-receipt, including when a receiver scans a SKU that isn’t on the PO: “You have exceeded the expected quantity for this product. Would you like to proceed ?” Can only be turned on when Allow Exceed Quantity is on | Receiver confirms the warning and continues |
Auto Complete Purchase Order | Completes the PO automatically when the last open line is received | Last line received, PO moves to Completed |
Auto Fill Attributes on Receiving | On mobile, pre-fills Lot Number, Expiry Date and Production Date from the PO line when the receiver scans a product. See Auto Fill Lot, Expiry, and Production Date During Receiving | Lot LOT123 filled in from the PO line |
Lot Batch Number Match | If the PO line has a lot number, only that lot can be received. If the line’s lot is blank, any lot can be received | Line lot LOT123: scanning LOT999 is blocked |
Expiry Date Match | If the PO line has an expiry date, only that date can be received. If it’s blank, any date can be received | Line expiry 31 Dec 2026: other dates are blocked |
Production Date Match | If the PO line has a production date, only that date can be received. If it’s blank, any date can be received | Line production date 01 Jun 2026: other dates are blocked |
Allow Update When Started | When on, PO lines that haven’t been received can still be edited after receiving starts. When off, lines are locked once the PO is Started, and receivers can’t add products during receiving, including with Create New Product on mobile | Off: a receiver can’t add a new SKU to a Started PO |
Allow One By One Receiving | Products are scanned one unit at a time on mobile | Each scan counts 1 unit |
Allow Create Without Product | Lets you save a PO without product lines, on the web, in Excel import and in the Open API | A PO created before the SKUs are known |
Pack Type Match | The received pack type must match the PO line’s pack type | Line in units: scanning a case is blocked |
Cross-Dock Receiving | POs of this type are received through the cross-dock flow on mobile. See Cross-Dock Receiving (Mobile) | — |
Mandatory Photo Capture During Receiving | Tooltip: “When enabled, item photo capture becomes a required step during mobile receiving for this Purchase Order Type. When disabled, photo capture remains optional.” Applies to mobile receiving only; the web Receive PO button isn’t affected. See Capture Product Photos During Mobile Receiving | Receiver can’t complete the receipt without a photo |
*Required
💡 The match parameters only check lines that have a value. To control which lot or date is received, enter it on the PO line.
How pack types are counted
If a receiver scans a different pack type of a SKU that’s already on the PO, Logiwa IO adds the quantity to that line using the UOM equivalent. No extra line is created. If Pack Type Match is on, the different pack type is blocked instead.
Example: A line orders 10 cases of 6 units. With Pack Type Match off, a receiver scans 12 single units, and the line shows 12 of 60 units received. With Pack Type Match on, scanning a single unit is blocked.
Changing a PO type that’s in use
Changes to a PO type apply immediately to every PO of that type, including POs already being received.
Example: You turn off Cross-Dock Receiving on a PO type. Receivers who scan those POs on mobile are routed to standard receiving.
Managing PO types through the Open API
PO types can also be managed with the Open API DataSetup endpoints:
POST /v3.1/DataSetup/purchaseordertype/createGET /v3.1/DataSetup/purchaseordertype/list/i/{index}/s/{size}PUT /v3.1/DataSetup/purchaseordertype/update
Common questions
A receiver added a product that wasn’t on the PO. How do I stop this? Turn off Allow Update When Started or Allow Exceed Quantity on the PO type. Receivers can only add SKUs that aren’t on the PO when both are on.
Can I receive a Completed PO? No. Receiving isn’t possible on a PO with the Completed status, whether it was completed automatically or manually.
The PO line has no lot number, but Lot Batch Number Match is on. What happens? Any lot can be received. The match only applies when the PO line has a lot number.
Can one line be received in both units and cases? Yes, if Pack Type Match is off. Both are added to the same line in UOM.