All documentation · Plugin overview
Data, integration boundaries and maintenance
Understand what this version stores and what remains internal.
Version 0.4.0-alpha.2 · Development candidate · Updated 25 September 2026
Ownership
WooCommerce owns checkout fields, validation, prices, taxes, shipping, payments and orders. Checkout Customizer owns presentation and progressive navigation. The classic renderer uses native checkout hooks and separates the native review and payment regions without intentionally duplicating payment. Blocks uses the existing page content.
Configuration and exports
The local hs_checkout_layouts_state_v1 option stores schema2, draft, active, previous and a named design library. This is an internal format, not a stable write API. Use the editor or validated JSON import. Exports contain presentation settings; imported image IDs are reset. Do not replace options directly on customer stores.
Public API
No product-specific stable extension hooks or public CRUD endpoint are declared in this release. Internal callbacks and classes may change. Native Woo hooks remain subject to the provider’s own classic/Blocks support. No API access or AI integration is promised.
Privacy and lifecycle
No remote fonts, tracking service or separate customer-data store is added. Existing WordPress media and Woo data retain their own policies. Deactivation and plugin deletion retain configuration. The plugin does not delete orders or rewrite the original checkout page. Back up database and plugin files before updating; reinstall the prior matching package to recover code and restore a suitable configuration.
Licensing and checkout operation
The package includes the shared HookSpark license client for connecting update and support entitlement through the Licenses page. Expired entitlement or an unavailable license server does not disable the installed checkout. Subscription billing and delivery of updates belong to the commercial services, not the layout or field editor. The presence of the client does not establish that purchase, renewal or delivery of this release has been verified. Keep license keys out of exported designs.
Order field snapshots
Read the private array with $order->get_meta(“_hs_cl_fields_v1”). Entries are keyed by stable field key and contain label/value strings. Use WooCommerce CRUD; HPOS is supported. This is a versioned internal storage detail, not a new stable public hook. Definitions live under fields.native and fields.custom in draft/active/previous settings. Values are included in WooCommerce privacy exports and removed by WooCommerce order personal-data erasure, subject to its erasure settings.
Recovery behavior in 0.4.0-alpha.2
Invalid persisted active settings fall back to disabled defaults; invalid draft settings fall back to valid active settings. Reads do not repair or rewrite stored configuration. Configuration writes must be confirmed before the admin announces success. These are internal implementation behaviors, not a new public settings API. The exported design format remains schema 2 and does not contain shopper answers.