Pallets

Overview

Pallets are handled as a dedicated package type (Pallet) and are intended for rule-based pallet optimization.

Product-based pallet rules

Pallet optimization rules can target a specific organization product attribute or product category. Choose one of the following product-match modes:

• EXACTLY: exactly the configured number of product units in the order have the selected attribute or category.
• AT_LEAST: at least the configured number of product units have it.
• ALL: every product unit in the order has it.
• NONE: no product units have it.

Quantities are evaluated as product units, not order lines. For example, an order line with quantity 3 contributes three matching products. Category matching follows the product category hierarchy, so a rule targeting a parent category also matches products assigned to its descendant categories.

For EXACTLY and AT_LEAST, the API stores the configured product count in minVolumeThreshold. The count must be a whole number of at least 1; ALL and NONE omit the threshold.

For configuration in the API, pallets use explicit dimension fields:

• length, width, height for inner dimensions
• outerLength, outerWidth, outerHeight for outer dimensions
• standard package fields such as name, material, max supported weight, and fold behavior

API behavior

Pallet writes use a single upsert endpoint:

• Upsert: repo.UpsertPalletPackage (insert when the pallet ID does not exist, update when it does)

Pallet reads use dedicated pallet endpoints:

• All pallet packages: repo.GetPalletPackages

Storage behavior

Pallet package geometry is stored in a dedicated table (package_pallet), separate from package_fixed.

Scope presets

Scope provides pallet presets as templates to speed up onboarding. You can still create custom pallets with your own dimensions.