Skip to main content

Enterprise features

Current API source catalogs six fields under Enterprise features:

  • sharing order details and its expiry;
  • international phone validation;
  • store switching from cart;
  • confirmation-page design; and
  • upselling type.

The preserved capture contains historical field labels and is fixture evidence, not a current response or deployed inventory. Current API source defines shared-order expiry in days; it does not prove a configured value, deployed unit/effect, option selection, customer exposure, checkout behavior, or successful outcome.

Historical Enterprise feature controls fixture without configuration values

Selecting a returned category performs authenticated reads. The shared editor can persist changed configs sequentially, so later failure can follow earlier persistence. Sharing, contact validation, cart, confirmation, upselling, order, customer, and product-builder effects remain blocked and untested.

Runtime re-entry requires an approved synthetic Enterprise project, intercepted category/config reads and writes, masked order/customer fixtures, and immutable receipts for each downstream consumer. A missing field does not identify entitlement, deployment, or configuration cause.

Related guides: Enterprise settings