v1.017

SSCC unification. The deprecated sscc field on the Create Receiving endpoint now accepts both the 18-digit GS1 SSCC and the 20-digit form with the leading GS1 AI "00" prefix. All API responses now return the 20-digit form consistently. The cartons[].identifiers / pallets[].identifiers SSCC values behave the same way.

🚀 New Endpoints

None

🛠 Schema & Property Updates

• Create Receiving (POST /v1/integrations/receivings) — the deprecated sscc request property previously required exactly 18 digits (minLength: 18, maxLength: 18, pattern: ^\d{18}$). It now accepts 18 or 20 digits: minLength: 18, maxLength: 20, pattern: ^(00)?\d{18}$. The value is normalized to 20 digits on storage; the same rule applies to cartons[].identifiers and pallets[].identifiers entries with type=SSCC.

📖 Documentation & Constraints Changes

• Create Receiving — the sscc request property description now states: "Accepts 18-digit GS1 SSCC or 20-digit form with leading 00; stored and returned as 20 digits."
• Receiving identifier value — the value property on cartons[].identifiers / pallets[].identifiers items now documents: "For type=SSCC, must be a valid GS1 SSCC — 18 digits or 20 digits with leading 00; stored and returned as 20 digits."
• Get Receiving — the deprecated sscc response field description now clarifies: "Always returned as 20 digits (GS1 AI 00 prefix included)." No runtime change for callers that already accepted the field as a string; clients that hard-coded a length of 18 must accept 20.