Executive Summary
Most warehouse operations have a unique pick process. Many have a clear pick pack ship process, but few have an equally clear pack and ship process, and almost none have an automatic connection between the shipment event and the ERP financial postings that should follow it.
This creates a gap between when the truck leaves and when the invoice is sent out, and also a gap between when inventory physically leaves the building and when the ERP shows it.
This guide describes how each step of the pick pack ship process should work and what the ERP financial handoff looks like when warehouse execution and financial systems are properly wired together.
What Happens Between Pick Completion and Invoice: The Pick Pack Ship Process
The typical pick to pack workflow starts with the picking. The picker checks that the order is complete and puts the items in a tote or cart before going to the packing area.
The gap most operations carry sits between the truck leaving and the ERP being told
Pick completion
The picker checks that the order is complete and puts the items in a tote or cart before going to the packing area.
Packing station
The order then moves on to a packaging station where the packer confirms the items picked, chooses or is supplied with the correct carton, inserts the protective packing materials, seals the package and prints the shipping label.
This picking and packing sequence makes sure the order is ready for dispatch.
Manifest and load
Ship: the next step in the pick pack ship process flow is to ship. Packed cartons are manifested, staged by carrier and loaded onto outbound trucks per carrier schedules and cutoff times.
Where the ERP falls behind
But in many pick pack and ship warehouse operations, the ERP update is still a manual task. Someone has to confirm shipment, close the sales order and generate the invoice, sometimes hours after the truck has left, or even the next business day.
That delay is more than an administrative backlog. The disconnect between the physical shipment and the ERP financial posting is the root cause of many revenue recognition errors, inventory discrepancies and carrier claims.
Let’s
Talk
Book your manufacturing AI strategy session
Cartonization: Automating the Box Selection Decision
Cartonization is the algorithmic process for determining the optimal box size and item configuration for a shipped package. It aligns each item's dimensional and quantity characteristics with the available carton sizes in order to minimize dead space, reduce dimensional weight (DIM weight) charges, and eliminate the need for packers to manually guess at box selection.
Why it matters: most carriers calculate shipping on dimensional weight, which is based on the space a package takes up, not just the actual weight. In other words, it might be more expensive to ship a light product in a big box than the same product in a properly sized carton. When you ship hundreds of packages a day, the lack of consistent box choice becomes a measurable shipping cost.
Manual packing varies: a packer on a deadline might take a box that is "close enough," while another might experiment with different sizes on a slower shift. Over-packing requires more void fill and allows items to shift in transit. Under-packing can leave products inadequately protected, increasing the risk of damage and carrier claims.
Smart cartonization takes the guesswork out of the process by suggesting the right sized box for each shipment.
Consistent carton choice is a measurable shipping cost, not a packer preference
What the Cartonization Algorithm Takes In and Gives Back
- Item dimensions (length x width x height)
- Weight
- Fragility indicators
- The list of carton sizes available in the warehouse
- Assigned carton type
- Recommended item placement
- Estimated dimensional weight
- Void fill estimate
3D bin-packing optimization is applied to find the best box, minimizing wasted cube space while adhering to weight restrictions, fragile handling guidelines, and regulatory requirements, such as those for hazardous materials or liquids.
There are a number of ways to deliver this logic. Dedicated cartonization software platforms such as Paccurate, Descartes and nShift expose APIs that integrate with a WMS or ERP at the packing station.
Many of the high-end WMS systems, such as Manhattan and Blue Yonder, have cartonization modules built in. But mid-market systems differ in their capabilities. For manufacturers on NetSuite, SAP or Epicor, cartonization can also be deployed as an ERP-connected middleware layer.
GrayCyan builds that middleware for mid-market manufacturers with accurate item dimensions in their ERP to connect item master data directly to packing station carton selection, eliminating the need to purchase standalone cartonization software.
Packing Station Setup and Packing Verification
At the warehouse packing station, pick accuracy is verified and packing errors are caught before they become customer returns or shortage claims. Most operations are heavily investing in picking but under-investing in packing station design and verification logic. Even if a pick is done well, the final step of packing can ruin it if it is inconsistent or rushed in a busy pick pack and ship warehouse.
Effective Warehouse Packing Station Layout
Plan the throughput
Each station should have a staff size and number commensurate with the anticipated carrier cutoff volume. For example, a station expected to process 60 cartons an hour must have enough space, equipment and labour to keep that pace. If packing falls behind, shipments miss carrier cut off times, delaying the entire outbound operation.
Check the item before sealing
Each item in the sales order is scanned to ensure the right SKU and quantity is in the box. This is the final practical opportunity to spot picking mistakes. Once the carton is sealed, correcting an error typically involves opening it again if you are at the shipping dock, or handling the problem as a customer return.
Decide the carton first
Carton selection also needs to be decided prior to packing, either through cartonization software or a defined manual process. The packer should not select the box after the items have been placed on the station.
Stock the station fully
Every packing station warehouse should be fully stocked with tape, void fill, dunnage, fragile labels, hazmat stickers and other materials. Regular visits to a central supply room prevent interruptions to packing throughput.
Scan at multiple points
Packing verification typically includes multiple scan points. Item barcodes verify the right SKU and quantity, and lot-tracked products require scanning with a lot number.
Capture the lot as a CTE
This packing event is a Critical Tracking Event (CTE) under FSMA 204 because the lot number and destination must be captured. Learn more about how to do this using lot traceability software.
Check weight and serials
Actual carton weight should be compared to expected order weight and large variances flagged for review prior to printing of the shipping label. For serialized products, serial numbers should be captured against the sales order line before the carton is closed.
Does Your Packing Station Talk to Your ERP?
20 minutes. Tell us which ERP you run and whether shipment confirmation posts COGS and closes the sales order on its own, or whether someone updates it the next morning.
Shipping Automation: Carrier Integration, Label Generation and Manifesting
Shipping automation links the packed carton to the carrier systems that will transport it. At a minimum you could do some label generation against the sales order. More sophisticated pick pack ship automation includes carrier rate shopping, batch manifesting and proof of delivery capture.
The goal for a modern pick pack ship software workflow is to eliminate manual hand-offs between packing station, carrier platforms and ERP.
The label, the tracking number and the ERP order should be one event, not three
Carrier rate shopping
Shopping rates begin with carrier integration. A WMS or warehouse shipping automation software platform can query multiple carrier APIs in real-time at the packing station to compare the available services and costs and select the option that meets the required delivery timeline.
Label generation
The system immediately creates a carrier-compliant shipping label once the carton is selected and weighed. This prevents errors in manual data entry and prevents the situation where labels are printed in advance and placed on the wrong cartons.
Tracking number capture
Another critical step is the capture of the tracking number. This should be automatically writing back the carrier tracking number at label creation to the ERP sales order, rather than requiring someone to update the order later.
Manifesting
Manifesting completes the outbound shipping cycle. The WMS should produce batch manifests including the carrier bill of lading, end of day scan, and confirmation of carrier pickup. For multi-pickup operations, manifesting should be based on carrier cutoff times, not manual triggers.
Native fulfillment links order shipment confirmation with financial posting (including inventory adjustments and sales invoice creation) for NetSuite pick pack ship workflows. However, NetSuite does not handle the creation of physical carrier labels itself. Therefore, it is common to integrate with services like ShipStation, EasyPost, or direct carrier APIs to accomplish this.
Same is true for SAP and Epicor: ERP handles order and financials, middleware connects to carrier systems. Where WMS and ERP are separate, the shipment confirmation event has to write back to the ERP outbound delivery and this is where many manual re-entry problems can occur.
Let’s
Talk
Book your manufacturing AI strategy session
The Financial Handoff: What Happens in the ERP When a Shipment is Confirmed
When a loaded shipment leaves the dock, three things should automatically occur in the ERP, and in most mid-market operations, at least one of them will require manual labor.
The step from warehouse to accounting in the financial handoff is the one that most warehouse operations guides completely skip. A shipment confirmation is not just a warehouse event in a connected pick pack ship process. It is the driver behind a number of financial and operational updates:
Sales order close
The open line on the sales order is closed and the quantity shipped is confirmed against the quantity ordered. Any back orders, partial shipments, or over shipments are flagged for review.
In ERP terms the delivery document is goods issued. It decreases the open order balance.
Inventory credit and COGS posting
The ERP should post the financial impact when inventory is removed from the building. The system debits Cost of Goods Sold (COGS) and credits Inventory at the standard cost or average cost of the shipped items.
If this warehouse process for COGS posting is delayed, ERP inventory levels can show more stock than physically available. This has an effect on inventory accuracy, which is a crucial aspect of effective ERP inventory management.
Post to accounts receivable
The ERP posts the customer obligation upon shipment confirmation and commencement of invoicing. The usual accounting entry is a Debit to Accounts Receivable and a Credit to Revenue.
If invoicing is not linked to shipment confirmation, revenue recognition could occur on a different day than when the shipment physically occurred.
Outbound delivery posting
The ERP delivery record should include the actual quantity shipped, carrier tracking number and ship date.
This creates the audit trail to connect the physical shipment to the financial records.
The breakdown generally occurs when the WMS and ERP are not integrated. The warehouse ships with pick pack and ship software and then someone manually updates the ERP the next morning. COGS and revenues are posted late, inventory is overstated overnight, and tracking info can get stuck in shipping systems rather than showing up on the customer order.
The target state is simple:
Shipment confirmation in the WMS automatically triggers the ERP goods issue, COGS and inventory journal entry, tracking number update, and invoice generation within seconds of carton manifestation. The warehouse team does not need to touch the ERP and finance does not have to wait for manual updates. The outbound process features an automatic financial handoff.
Connecting Pick Pack Ship to the ERP: What GrayCyan Builds
Most mid-market manufacturers on NetSuite, Epicor, SAP, Acumatica, Fishbowl or Odoo have the native ERP functionality to post the financial handoff automatically. What is missing is the middleware, the link between what happens at the packing station and what the ERP needs to know.
Verification scans post to the ERP fulfillment record, not to an end-of-day batch
Packing Station Scans Into ERP Transactions
- GrayCyan develops the integration layer connecting the physical pick pack ship workflow with ERP transactions.
- This includes the packing station scan integration where item verification scans update directly to the ERP fulfillment records rather than separate entry or end of day batch updates.
- The shipment confirmation from the packing workflow can then trigger the ERP goods issue posting including COGS debit, inventory credit, sales order closure and AR invoice generation.
Packing as the Last Traceability Touchpoint
- Another critical connection point is lot traceability. Captured lot numbers at time of packing confirmation can be written back to ERP lot history and FSMA 204 Critical Tracking Event records, making packing the last traceability touchpoint before products leave the facility.
- These integrations form part of GrayCyan's approach to custom WMS development, linking warehouse execution to business systems.
- GrayCyan also helps manufacturers implement ERP AI automation, where smart workflows can reduce manual handoffs across operations.
Packing is the last point a lot number can be captured before the product ships
What the same scan-to-ERP integration delivered on a Fishbowl ERP build
GrayCyan has connected pack-ship workflows to NetSuite, SAP, Epicor, Acumatica, Fishbowl, Odoo and Microsoft Dynamics 365.
Let’s
Talk
Book your manufacturing AI strategy session
Frequently Asked Questions: Pack, Ship, and Financial Handoff
Gaps Between Your Warehouse and ERP at Pack and Ship?
Tell us what ERP you are on and where the disconnect is, whether it is carton selection, packing verification, carrier label generation, or the COGS and inventory posting that should occur at shipment confirmation. GrayCyan will demonstrate what connecting your packing station to your ERP truly means, from warehouse execution to financial handoff.
