Understanding the techOMS Packing Module [Information]

Modified on Tue, 9 Jun at 5:55 PM

The techOMS packing workspace provides a native manual fulfillment alternative for businesses operating without an external warehouse management application. This guide covers the core concepts, eligibility rules, and inventory logic behind the module.

 

 
WarningThe techOMS native packing module is currently in Beta. Advanced features, such as hardware barcode scanning, automated rate shopping, and strict Lot and Serial number validation, are deferred to future updates. 
 

 

TABLE OF CONTENTS


Eligibility and Configuration Rules


To utilize the native packing workflow, your account, orders, and specific fulfillment nodes must meet strict configuration criteria. The system bypasses external communication pathways to allow direct manipulation of shipments within the techOMS user interface.


Warehouse Application Requirements


Your target Warehouse must operate independently. During creation, its Application Type must be explicitly set to None.



This setting automatically hides external synchronization tabs within the associated Fulfillment Channel interface, dedicating the workspace solely to manual packing. For detailed conceptual information and advanced configuration, refer to How to Manage Organization Warehouses: Create, Edit, and Delete [Step-by-Step Guide].


Order Eligibility


For a shipment to be processed through the native packing workspace, its Requested Warehouse must be assigned to a facility configured with the None application type. Orders routed to standard warehouses linked to external systems will bypass this module and follow standard external fulfillment pathways.



API v1 Workflow Incompatibility


The packing module relies entirely on internal shipment generation and is strictly incompatible with legacy workflows that require external systems to manually inject shipment data.

 

 
WarningIf the Enable automatic sales order workflow account toggle is set to No, the packing module will fail. This configuration forces reliance on legacy API v1 workflows, breaking the native techOMS package generation.

 
 

 

For detailed conceptual information and advanced configuration, refer to How to Edit an Account [Step-by-Step Guide].


Inventory Impact Logic


Moving a shipment through the manual packing workspace protects your physical stock counts until final dispatch.


When an order reaches the Ready To Send status, the system secures the required items by increasing the Allocated Quantity. Progressing the shipment into the Packing or Packed statuses has absolutely no further impact on your Total Quantity, Allocated Quantity, or Available Quantity. The application is simply organizing allocated items into physical boxes.


Inventory is only definitively decremented once the fully packed shipment officially reaches the Shipped status. For complete details on how different statuses affect your stock, refer to Understanding Inventory Levels and Order Status Impact [Information].


Known Limitations and Exclusions


Certain techOMS features remain incompatible with the native packing framework during the Beta phase:

  • Time and Transit (TNT): Do not use a Warehouse assigned the None application type within any Calculate Time & Transit action, as external mappings are required to calculate rates. For detailed conceptual information and advanced configuration, refer to How to Use the Calculate Time & Transit (TNT) Action [Guide].
  • Hardware Integration: Dimensional scales and hardware barcode scanners are unsupported. You must manually key all dimensions and tracking data into the techOMS interface.


Next Steps


Once you verify that your account and warehouses meet these operational rules, you can begin executing orders. For complete procedural instructions on navigating the workspace and building packages, refer to How to Pack Shipments [Step-by-Step Guide].

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article