v1.3.0

Adds lot requirement settings to order creation, allowing merchants to specify minimum shelf life and specific lot controls at the order level or per individual order item.

🛠 Schema & Property Updates

Lot Requirements for Order Creation

Create Order (POST /v1/integrations/order): Added two new optional fields to the request body to support lot management during order creation.

• minimum_shelf_life_days (integer|null) — Sets a minimum shelf life requirement for all items in the order. The value must be greater than 0. When set at the order level, per-item lot_requirements must not be used.

• items[].lot_requirements (object|null) — Allows specifying lot controls per individual order item. Cannot be combined with the order-level minimum_shelf_life_days. Contains:

  • minimum_shelf_life_days (integer|null) — Minimum shelf life for this specific item (value must be > 0). Cannot be combined with lot_controls on the same item.
  • lot_controls (array<object>) — List of specific lot requirements for this item. Each entry may contain:
    • lot_number (string|null) — The required lot number.
    • expiration_date (string|null, format: date) — The required expiration date in ISO 8601 format (e.g. 2026-12-31).

📖 Documentation & Constraints Changes

• Create Order (POST /v1/integrations/order): Added a "Lot requirements" section to the endpoint description. It documents the mutual exclusivity rules between order-level and item-level lot settings, explains that lot requirements not applicable to a mapped bundle will result in the item mapping ending with "action required", and clarifies that new API requests override any manually set lot requirements (and that sending empty lot settings removes existing restrictions. Contact your happiness manager to enable lot management.