What launched on October 8

On October 8, 2026, Zenkraft announced that Zenkraft Shipping for Agentic Commerce was available in the Commerce App Registry. It is an app for Salesforce B2C Commerce Storefront Next intended to add estimated delivery dates, branded tracking and returns without separately integrating each storefront component. [1 · Zenkraft via Business Wire · app launch · October 8, 2026]

The wording “available now” establishes a launch rather than a promised pilot. The source is nevertheless the vendor’s own press release: it contains no public price, installation count, merchant review or order-performance data. [1 · Zenkraft via Business Wire · app launch · October 8, 2026]

Salesforce had already made Storefront Next generally available and named Zenkraft among the Commerce Apps Framework launch partners. Platform documentation describes installing registry apps through Business Manager. That supports the distribution mechanism, not Zenkraft’s claimed savings in time and cost. [2 · Salesforce · Agentforce Commerce and Storefront Next] [3 · Salesforce Developers · Commerce Apps architecture]

Where installation ends and implementation begins

An installable app can reduce storefront-level code because the vendor packages interface and server logic in a maintained extension. Yet “without bespoke integration” does not mean “without configuration”. Zenkraft’s guide requires the merchant to select a carrier, enter an account number or API credentials, and set sender details, currency, label format, dimensions and weight units. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [3 · Salesforce Developers · Commerce Apps architecture] [5 · Zenkraft · shipping setup guide]

The operating scope extends beyond installation. Retailers must test delivery-time and rate calculations for their warehouses, order cut-offs, unavailable services, split shipments and returns. A mistake in any rule can produce an unfulfillable delivery promise even when the app itself installs correctly. [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

The claim of more than 200 supported carriers applies to Zenkraft’s wider platform. Launch materials do not show which connections, countries and features are equally available in the new Storefront Next app. Coverage therefore has to be verified against each carrier contract and a test order. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

How a merchant should measure value

The business baseline is not the installation itself but the cost of the previous process: building and maintaining connections, manually preparing labels, “where is my order” contacts, missed delivery promises and return handling. After launch, the same measures should be compared across equivalent orders and lanes. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

A minimum implementation dashboard should include the share of orders with a valid promise, promised-versus-actual delivery variance, label-creation success, tracking-event latency, self-service return share and support contacts per thousand orders. Licence, configuration, carrier work, maintenance and error costs belong in the calculation. [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

Neither Zenkraft nor Salesforce published a merchant result, controlled comparison or payback period for this launch. The defensible conclusion is narrower: Storefront Next now has a standardized connection point for shipping, while its economics depend on the merchant’s starting complexity and configuration quality. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [2 · Salesforce · Agentforce Commerce and Storefront Next] [3 · Salesforce Developers · Commerce Apps architecture] [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

Expert commentary

The launch matters because shipping becomes part of an extensible commerce platform instead of a separate project beside the storefront. When estimates, tracking and returns are packaged as a Commerce App, updates can be applied repeatedly across stores. That could reduce technical debt, but only the installation channel—not the size of the savings—is confirmed. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [2 · Salesforce · Agentforce Commerce and Storefront Next] [3 · Salesforce Developers · Commerce Apps architecture]

The competitive mechanism works both ways. Salesforce strengthens Storefront Next with ready-made modules, while Zenkraft reaches merchants inside Business Manager. This can speed selection for a retailer, but it also increases dependence on compatibility between two vendors. Buyers need an update policy, support boundaries, data export and rollback procedure before signing. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [2 · Salesforce · Agentforce Commerce and Storefront Next] [3 · Salesforce Developers · Commerce Apps architecture]

Customer value begins before payment and continues after it. A credible date and transparent delivery cost reduce uncertainty at purchase; tracking and accessible returns reduce post-purchase effort. Yet the interface can confidently display a wrong promise when the warehouse calendar, cut-off or carrier service is misconfigured. Automation amplifies good rules and bad ones alike. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

“Agentic commerce” in the product name does not mean the module independently selects carriers or makes unrestricted decisions. Published materials describe data and actions that Salesforce and Agentforce processes can use. The merchant’s rules, allowed actions and exception controls determine autonomy; the product name alone does not. [2 · Salesforce · Agentforce Commerce and Storefront Next] [4 · Zenkraft · shipping and returns for Agentforce]

The social effect is local but tangible: accurate promises and self-service returns save time for shoppers and support teams. The trade-off is concentration of order, shipment and return history in one cloud workflow. Merchants should apply role-based access, retain an action log and decide which data is actually required for each operation. [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

Over the next quarters, maturity will be shown not by the number of carriers in a catalogue but by error-free orders on real lanes. Watch deployment time, label success, delivery-promise accuracy, tracking latency, self-service returns, contacts and total order cost. Until those data appear, this launch is an infrastructure option, not demonstrated payback. [1 · Zenkraft via Business Wire · app launch · October 8, 2026] [4 · Zenkraft · shipping and returns for Agentforce] [5 · Zenkraft · shipping setup guide]

Sources

  1. Zenkraft via Business Wire · app launch · October 8, 2026 — Vendor statement on registry availability, features and expected reduction in bespoke development; it provides no quantitative results or pricing.
  2. Salesforce · Agentforce Commerce and Storefront Next — Official account of Storefront Next general availability, the Commerce Apps Framework and launch partners including Zenkraft.
  3. Salesforce Developers · Commerce Apps architecture — Official documentation on installing registry apps through Business Manager and on the extension architecture.
  4. Zenkraft · shipping and returns for Agentforce — Vendor description of order-status automation, returns, shipping data and claimed support for more than 200 carriers.
  5. Zenkraft · shipping setup guide — Documentation covering carrier selection, API credentials, test mode, currencies, labels, dimensions and weight.