Product updates across Onebeat

Each capsule combines a product scope, a store scope and a validity window. Teams can publish it in stages, then deactivate or delete the rule when it is no longer needed.

This gives campaign and merchandising teams a repeatable way to coordinate curated collections across a selected part of the store network.

The policy defines the recurring shipping cycle for a store and product. Replenishment generated within that period is grouped into the cycle’s order and assigned to the first possible shipping day.

The result is a structured shipping rhythm that replaces scattered orders with a calendar the operation can plan around.

The manual path supports both the product matrix and the grouped forecast, supplementing the existing automatic integration when a team needs to provide the files directly.

The reported speed improvement is the measured result for the release benchmark; actual import time will depend on the file and environment.

The new analysis axis groups the Product Health view by valid collections. It complements the existing perspectives without changing the underlying product data.

This makes it easier to review the condition of a curated assortment or collection as a distinct part of the portfolio.

The analysis now focuses on the intersection of one store and one product group. This provides a more precise view than a broader network or category rollup when the team needs to understand a local assortment result.

Using the same level of detail as the allocation engine also makes the analysis easier to compare with the decisions that follow.

Store eligibility is evaluated using location-level conditions available to the retailer, including attributes such as region and store type.

This supports seasonal definitions that vary across the network while keeping the scope tied to the stores’ own operating characteristics.

The indicator set has expanded to include seasonality across the screen’s views and at both SKU and product-color level. Total target stock, also called buffer, is shown at product level.

These additions help users distinguish the current stock position from the target used to guide inventory decisions. They build on the existing catalog workspace and its detailed product and store views.

The detail view brings together the parent and substitute items, replenishment quantities, active minimum and maximum limits, and any rules that prevent supply. Sales, availability, stock and transit provide context for an edit.

Import templates support broader updates, while the finer store-product-size limits give teams control over individual cases.

Store-level conditions narrow the network used for stock, sales, sales rate, coverage, sell-through and store counts. The scope preview uses the current configuration choices so teams can inspect the proposed analysis before running it.

Head, Belly and Tail classification remains based on the whole-network ranking. The screen identifies that distinction so a strong national performer is not automatically read as a strong performer in every regional cut.

Select multiple rows in the By Route, By Store or By Product Color view. The transfer cards and lower detail views use that selection while the aggregate table remains available for comparison.

A route is treated as one donor-receiver pair. Selecting two routes does not introduce additional combinations between their stores. The interface keeps the selection count visible and provides one action to clear the scope.

The catalog combines target stock, inventory KPIs and product and location attributes at the store-SKU level for each distribution-center point. This gives the warehouse team a consistent starting point for inventory review.

The view complements Onebeat’s store-facing inventory workflows by making distribution-center context available in a dedicated catalog.

Search and paginated value lists help users find the relevant source values beyond the first page. A selected-values view makes multi-value conditions easier to check.

Column guidance explains accepted values and validation requirements, including whether a check blocks saving or only warns. Orders can be mapped through the same workbench pattern as other integration entities. Clearer field-to-system mapping and value counts help users review the source catalog.

The workflow combines inventory coverage bands with Head, Belly and Tail performance classification. Size-level detail shows the proposed purchase quantity needed to support the selected coverage target.

Teams can preview the portfolio in scope, inspect the supporting detail and export the results. These are recommendations for review; the workflow does not automatically change stock targets, supply restrictions or replenishment lists.

The workflow supports product and store scope, including store clusters, and compares the projected inventory requirement with stock available at the distribution center.

The simulation makes the expected need and the portion that supply can fill visible together. Planners can use that information to review a recurring season or one-off campaign and identify the gaps that need a preparation decision.

The workflow combines retailer-specific product, SKU, store and SKU-store filters with supply-origin context and substitute visibility. Teams can apply mandatory supply restrictions, known in Onebeat as avoids, to individual rows or a wider selection.

A 180-day SKU-store history shows stock, sales, in-transit inventory, rolling sales and target-stock changes. This supports investigation of the current position before the team adjusts a rule or takes another inventory action.

Teams build conditions from the retailer’s available attributes and operating measures, then choose the supported action. The attribute catalog reflects the data available for that retailer.

Only active rules are applied during processing. This gives teams a way to prepare and review changes before making them part of the operating cycle.

Recorded checks can show the relevant rule, observed value, threshold and decisive step in the allocation process. Run logs and product-level summaries help place those checks within the selected allocation method and scope.

The detail available depends on the supported method and scenario. The improvement adds useful review evidence without changing the need for the team to assess the operating context.

Grouped store and product views bring a large run into a more manageable review structure. Route-level reasons explain the conditions behind supported donor-receiver decisions.

The transfer logic also considers isolated-size consolidation and stock already received by donor stores. Origin traceability helps the team follow the recommendation through the review.

The business-objective wizard organizes the settings used by Smart and Pack Replenishment into guided steps. Options and permitted ranges make the configuration easier to interpret.

Once the policy is configured, the expanded review filters help teams narrow a run by retail attributes and operating conditions. Existing governance controls continue to determine how recommendations move into action.

The workflow supports applying mapping logic across multiple entities. Validation covers required values, identifiers, units of measure and destination-specific rules.

Direct mappings, conditions and formulas let integration teams express how source data should be interpreted. This strengthens the data preparation underneath Onebeat’s inventory workflows.

The workflow lets users review product-colors through different performance metrics and move between chain and store perspectives. Filtering, sorting and export support analysis of the full selected portfolio.

Availability, store stock, origin stock and the selected HBT perspective provide context when the team inspects product detail. A product’s network ranking can then be considered alongside the local position that calls for action.

Users define the level of detail and select from approved fields and relationships. The workflow supports calculated measures and combined views, with sample results available for inspection before an approval request.

Revisions, version history and inactivation requests keep the view’s lifecycle visible. The governed catalog determines which data and relationships are available to use.

The configurable hierarchy lets teams choose the levels that fit their operating question. Status bands distinguish understocked, balanced, overstocked and no-sales groups within the analysis.

The same selected scope and weighted coverage logic carry through each level, helping the user connect an aggregate result to the store, product or size that needs attention.

Severity grouping and value-at-risk measures provide a basis for prioritizing the review. Users can then move through the shared hierarchy to inspect the product-color and store detail behind an issue.

Product, location, feature and retailer-specific filters help focus the investigation on the part of the operation the team manages.

Teams can compare 30-, 60- and 90-day sales windows and review richer financial summaries. Chain and store perspectives distinguish broad product performance from a local inventory problem.

The analysis helps identify where strong sellers need protection and where stocked low performers or no movers call for a closer decision. It supports the review; it does not automatically choose a markdown or transfer.