Reference for Shipping Order Rules and Limitations

The Shipping module is a fundamental tool for managing inventory shipment in the system, facilitating its planning, picking, and packing. To ensure efficient operation and avoid errors during processing, it is essential that users understand and comply with a series of established technical rules and limitations.

This article covers the following topics:

• General references for a Shipping order
  • Header-level information
  • Line-level information
• References for creating Shipping orders via API

General references for a Shipping order

Header-level information

• Ship to: Only pre-configured accounts in the system can be used.
• Shipping address:
  • If there are multiple shipping addresses configured at the account level, the first shipping address that was registered will be automatically assigned.
  • If there are no shipping addresses configured, but there is a billing address at the account level, it will be used as the default for shipping.
    • Additionally, the account name will be assigned as the recipient of the order.
• Billing address: 
  • If there are multiple billing addresses configured at the account level, the first billing address that was registered will be automatically assigned.
• Carrier: By default, it uses pre-configured carriers.
• Tracking number:
  • Entered manually by the user.
  • Character limit: 255.
• Estimated shipping date: Any date can be entered.
• Notes: Up to 65,000 characters can be registered.

Line-level information

• Part number:
  • Only part numbers previously configured in the system can be used.
• Required quantity:
• Packed quantity:
  • By default, the system allows indicating a packed quantity greater than the one requested. To disable this option, the "Validate that the selected quantity does not exceed the requested quantity" setting must be enabled at the account level.
• Location:
  • Must be pre-configured locations.
  • By default, the system allows picking inventory from normal or picking type locations.
    • To restrict picking to only picking type locations, enable the "Enable picking from picking locations only" setting at the account level.
• Label:
  • Must be of the same part number requested and be located in a valid location.
  • Inventory managed by part number: When inventory is managed by part number, the system, by default, will assign a virtual label that will not physically exist, nor is the user expected to scan it.
• Purchase order:  By default, the system assigns the purchase order number indicated at the header level.
• Serial Number:
  • Must correspond to the same part number requested.
  • Serial number management:
    • Must not have been previously shipped.
    • Must be available, not committed to another Shipping order.
• Part number description: Is read-only and shows the description configured for the part number.
• UOM Type: Is read-only and displays the type of unit of measure configured in the part number.

References for creating Shipping orders via API

Allows creating one or more orders with multiple lines through the API, following the general rules of a Shipping order, previously mentioned.

Important considerations:

• The user used for authentication via the API must have the necessary permissions to create Shipping orders.
• Line limit per request: 750.
• The total number of lines to be communicated is considered whether it is a single Shipping order or if multiple orders are being sent that, together, total 750 product lines.

Consequence of exceeding the limit:

• The system will not process the request.

Execution time: Approximately 43 seconds for an order with 501 lines.

Recommendation: Split the request into orders that, together, have fewer than 750 lines to optimize performance.