Package v20 major release - 1 July 2025

New features

• Cart Object Introduces a dedicated Cart object that collects items, pricing details, and order metadata, giving future enhancements a structured place to store persistent carts and discount rules.
• Store Path Removed from Builder and Console URLs Builder and console links no longer depend on store‑specific paths, easing navigation across environments and removing configuration steps.
• POS design for menus and interactions You can design exactly how your POS menu items appear and behave using actions and action groups. You can use them to initiate single actions, or chains of actions that simulate a workflow.
• POS Layout and Layout Field Adds a layout system and typed layout fields so checkout screens can be arranged differently for kiosks, mobile devices, or in‑store terminals without extensive code changes.
• Payment Provider Channel Adds a field on payments to note which processor handled the transaction, improving routing clarity and troubleshooting in multi‑provider setups.
• Payment Fingerprint Field Each payment now includes a fingerprint that helps detect duplicates and supports fraud‑prevention workflows.
• POS View Object Combines layouts and actions into reusable views, enabling consistent screen templates across kiosks, mobile checkouts, and back‑office stations.
• POS Next Action Item Allows a task to queue its successor, letting POS flows move automatically from scanning items to collecting payment and printing receipts.
• Improved Field‑Creation Tool Command‑line tooling now auto‑generates metadata and validation for new fields, reducing manual setup and errors.
• Zone_c.Strict_c Field Adds an optional Strict_c field to Zone records, which can enforce tighter location or compliance rules when needed.

Deprecated Fields

• Store Path Requirement The old need for store‑specific URL paths is deprecated. Integrations should move to the pathless format to remain compatible.
• ActionItem.label Renamed The label property was renamed to display_name for clarity. Codebases must update references to avoid missing data.
• User Flag Fields Removed from SC Sync Legacy user fields that interfered with sync reruns were removed. Systems should rely on the current validation flow instead.

Fixed Bugs

• Head Content Field Label Corrected a mislabeled head‑content field, aligning the UI with the underlying schema.
• Scheduled Job Queueing Ensures scheduled jobs can always enqueue, preventing gaps in automated payment or batch operations.
• Unique Strings for Custom Mapping SC Sync now assigns unique strings to custom mappings, preventing collisions and inconsistent results during reruns.
• Question Label Replaced A “Question” label appearing in success states was corrected to “Success,” providing clear feedback to users.
• Obsolete User Flags Removed Deleting outdated user flags stabilised SC Sync and eliminated errors triggered by stale data.
• Package XML Linting Added linting for package XML files to catch structural issues before builds, improving release reliability.
• POS Metadata Labels Cleaned up mismatched labels introduced with the layout system, ensuring accurate references for developers.
• Sync Label Alignment Aligned naming across the Cart object and field‑creation tooling to avoid confusion and runtime mismatches.