TABLE OF CONTENTS
After orders are created in WarehouseOS, they are immediately sent to FitShipper. Any rules setup in FitShipper will run against the order.
During the Order creation process, if an order is identified as already existing in FitShipper, an update call will be made against that Order. This update call can update Order Lines, addresses, and trigger the rules to be rerun. Orders can be tagged and cleared in WarehouseOS to push an update to FitShipper.
Fitshipper can validate the address after the Order is created. WarehosueOS makes periodic calls to FitShipper to check on the results of any rules that are run. If the address is identified as Invalid, the order in WarehouseOS will be put on Hold and identified as Address Invalid. An optional email can be sent to notify someone to review and update the address.
The address will be fixed and re-validated directly in FitShipper. Periodic checks against FitShipper for orders with an invalid address will identify when the address has been corrected and automatically release the order in WarehouseOS so it can be batched and picked.
Package Details in WarehosueOS
WarehosueOS makes periodic calls to Fitshipper to check on the results of the rules. Carrier and Service details can be loaded to theOorder in WarehosueOS and used in the batching process. Packages assigned by the rules in FitShipper can be assigned to the Order in WOS.
If a Package is assigned by the Fitshipper Rules, and if those packages have a matching value inside WarehouseOS, the assigned package can be assigned to the Order in WOS. This will display the assigned package during the packing process in WarehouseOS, allowing the Packer to see which package size was used for the pre-generated label.
Item details are sent from WarehouseOS to PostageForce. These details include weight, value, HTS and Country of Origin, and categories that can be used in the Rules that are run.
The integration with the Host system can be configured that when certain details on the item are updated, the item is automatically flagged to push these updates to FitShipper.
Automated Label Creation
Upon request, the FitShipper integration can automatically generate shipping labels and print them at packing.
Implementing this flow requires the use of WOS Print Agent. When labels are pre-generated, FitShipper prevents duplicates labels from being created against the Order.
Timing of Labels
WOS starts the label generation after the Order is picked Complete. The shipping label is stored in WOS's Print Queue and then triggered to print when the Order is Packed.
Real-time Label Generation
Instead of generating shipping labels after Picking, the integration can wait for Packing. This would require the Packer to wait for a live call to FitShipper to be made before a label could print out. Depending on how quickly FitShipper responds to the label request, this could double or triple the time it takes to print a label.
FitShipper can generate a label by just providing the Order Number and using the results of the Rules that were run against the Order. If multiple Boxes will be sent on the Order, WOS can use the "Packing Box Closed" event to identify what is in the box and send a box weight and customs details to FitShipper to generate a box-specific label. A specific flag is sent to allow multiple labels to be created against the same Order, bypassing the duplicate label prevention.
Based on an Order Tag, print out a packing slip titled as "Pickup". This will skip the label generation and give the Packer a label to apply to the Order Details that are being picked up.
Manual Created Labels
If the auto-generated labels fail, labels against a given Order can be created directly in FitShipper. After the Order is packed, WarehouseOS will identify that the order is missing tracking details and make periodic calls to FitShipper to identify the tracking and pull those details back into WarehouseOS . This will then be used to provide tracking back to the Host system.
If a label that was automatically generated later needs to be voided, this detail will be brought back into WarehouseOS. A regular call will be made to identify labels that were voided. The WarehouseOS order will be updated based on these details. Many eCommerce systems don't allow Updates or Deletes once a fulfillment and tracking has been pushed, though an attempt will be made if possible. Instead of pushing the tracking back to the eCommerce system immediately after Packing, WarehouseOS can delay the initial push to the eCommerce site to provide a time period for.