.png)
A pick ticket selects what is actually available against a customer order, and in AIMS360 you cannot invoice without one. Three ways to create it, three picking methods, combine rules, ship complete enforcement, and scan to verify picking on a handheld.
An order says what a customer wants. A pick ticket says what you can actually send today, against real stock, in the right warehouse. In AIMS360 it is not optional paperwork: you cannot invoice an order until it has been picked, which is exactly why the picking rules are worth understanding before your warehouse inherits them.
A pick ticket selects the finished goods actually available against an existing customer order. Production is planned so every order can ship, but production runs short, goods get damaged and someone else's order gets there first. The pick ticket is where the plan meets the shelf.
A pick ticket is required before an invoice can be created. Every customer order has to be picked so that shipped quantities are reconciled against ordered quantities before anything is billed. That single rule is why the picking method you choose matters more than it looks.
The flow is short and it does not vary: a pick ticket is created, it goes to the warehouse whether that is your own floor or a 3PL, the picked quantities are confirmed or corrected against what was physically found, and the invoice is created from the final picked quantities. Not from the order. From the pick.
Open the order, tag the line items you want to pick, choose a picking method and create. The person creating it decides which orders and which lines go first, so order completion dates and priorities are on them to check.
Create pick tickets across a set of orders in one pass rather than opening each order. This is what most brands use once the order book is bigger than a person can sequence by hand.
Allocate stock across the whole open order book by rules rather than by order entry sequence, then create pick tickets from the result. This is the one that stops your best account losing units to whoever ordered first.
After a pick ticket exists, quantities remain editable per size. Line item notes from the customer order are visible in the pick and invoice view, which matters for brands who use notes to decide what gets picked when.
The picking method tells AIMS360 how to weigh what is on order against what is actually in stock. Pick the wrong one and you either short a customer or promise units you do not have.
| Method | What it does |
|---|---|
| Partial Recommended | Picks any quantity up to 100% of what is on order, based on existing inventory and unallocated goods. Ten units ordered against five in stock picks five. This is the most widely used option and the right default for most brands. |
| Complete | Only picks a line if 100% of the ordered quantity is available. One unit short and the line is skipped entirely. Useful when a partial shipment costs you more in freight and compliance than it earns. |
| Zero stock | Ignores system inventory completely and picks 100% of what was selected. Also called a forced pick ticket. It exists for specific situations and is not recommended for routine use, because it will happily pick units you do not have. |
All three methods work against the same stock figure the rest of AIMS360 reads, so a pick ticket immediately affects what order management shows as available and what publishes to your channels and to the 846 inventory advice.
| Option | Behavior |
|---|---|
| Do not combine | Never merges. Every creation makes a new pick ticket regardless of what already exists on the order. |
| Combine always | Merges the new pick ticket into any existing pick ticket on the same order. Not recommended, because it can quietly change a ticket the warehouse is already working from. |
| Combine if never printed Recommended | Merges only when the existing pick ticket has never been printed. That is the safe version: it consolidates paperwork without rewriting something the floor already has in its hands. |
Printing a pick ticket to the screen counts as printed. Preview it and AIMS360 records it as printed, which means combine if never printed will stop merging into it from that moment.
That is the correct behavior, because a ticket a person has looked at may already have been acted on. It surprises people the first time, so it is worth saying out loud during training rather than discovering it when a shipment goes out twice.
When an order is marked ship complete, 100% of the goods on that order have to be picked at the same time, and that overrides whatever partial or complete setting was chosen. Creating a pick ticket against a ship complete order produces a reminder that partial shipments are not allowed on it.
A user picking with zero stock is not notified that the order is ship complete. It is one more reason to disable zero stock at the user or warehouse level unless somebody has a concrete reason to need it.
Non inventory and service fee styles carry no physical stock, so the ship complete check only looks at inventory styles. As long as the real goods are there, the pick ticket is created and a freight or service line does not hold it up.
Print the ticket and hand it over. Plenty of warehouses still run this way and there is nothing wrong with it, as long as the picked quantities come back into AIMS360 before the invoice.
With mobile device scanning, a picker sees the tickets assigned to them, scans the bin location and then the UPC of each item. The device rejects a bin or a UPC that is not on the ticket, so the mistake is caught at the shelf.
Pick tickets can be assigned to a specific user, and on the handheld the scan option only appears on a ticket assigned to the person holding it. The ticket, the picker and the scan record stay tied together.
Export pick tickets to a warehouse as a flat file, through an API, or as an EDI 940 warehouse shipping order with the 945 shipping advice coming back. The picked and shipped quantities land on the same record either way.
Once the goods are packed, GS1 128 carton labels and the 856 advance ship notice are built from the same pack transaction, which is why the label and the ASN cannot disagree. The invoice then comes off the final picked quantities.
It is the document that selects the finished goods actually available against a customer order. Production is planned so every order can ship, but shortages and damages happen, so goods are picked against real inventory rather than against the order. The picked quantities are then what gets invoiced.
Yes. A pick ticket is required before an invoice can be created in AIMS360. Every customer order has to be picked so that shipped quantities are reconciled against ordered quantities before anything is billed.
Three ways. Manually from the pick and invoice tab of an order, by batch allocate picking across a set of orders at once, or through intelligent allocation, which allocates stock across the open order book by rules and creates the tickets from that.
Partial picks any quantity up to 100% of what is on order based on available stock, so ten units ordered against five in stock picks five. Complete only picks a line when 100% of it is available and skips the line otherwise. Zero stock ignores inventory entirely and picks everything selected, which is why it is also called a forced pick ticket.
Partial, for almost everything. It is the most widely used option and the one that behaves the way people expect. Complete is for programs where a partial shipment costs more in freight and compliance than it earns. Zero stock is for specific situations and should not be a habit.
Yes, and most brands should. Zero stock can be disabled per user in module permissions, or per warehouse so nobody can force a pick against that location at all. It is enabled by default, so switching it off is a deliberate decision rather than something that happens on its own.
They decide whether a new pick ticket merges into an existing one on the same order. Do not combine never merges. Combine always merges into any existing ticket, which is risky because it can rewrite a ticket the floor is already working from. Combine if never printed only merges into a ticket nobody has printed yet, which is the recommended setting.
Yes, and this catches people out. Printing a pick ticket to the screen marks it as printed, which means combine if never printed will stop merging into it from that point. That is deliberate: a ticket somebody has looked at may already have been acted on.
Ship complete overrides the picking method. All of the goods on the order have to be picked at the same time, and creating a pick ticket against such an order produces a reminder that partial shipments are not allowed. Note that a user picking with zero stock is not shown that warning.
No. Non inventory and service fee styles carry no physical stock, so the ship complete check only looks at inventory styles. As long as the real goods are available the pick ticket is created.
Yes. Pick quantities stay editable per size from the pick and invoice tab, which is how you handle the difference between what the system expected and what the warehouse actually found. Line item notes from the order are visible in that same view.
Yes, and on a handheld it matters: the scan option only appears on a pick ticket assigned to the person holding the device. That keeps the ticket, the picker and the scan record tied together rather than leaving an audit trail nobody can follow.
Show us how orders get picked today, who decides the sequence, and what happens when production lands short. We will show you what changes when the pick ticket, the label, the ASN and the invoice all come off one record.
