A category manager, an ecommerce lead and a Google Ads specialist can look at the same jacket and see three different things: a seasonal buying commitment, a product page and a set of feed items.
All three views are useful. They become difficult to coordinate when the business decides the jacket needs more support and nobody can follow that decision through to advertising allocation.
Expanly is built around that connection. The Control Layer for Retail Growth gives retail teams one product-priority model: connect commercial and performance data, define the rules, approve the changes, deliver a usable signal and review what followed.
The work behind it is technical. The test of it is practical: can the team explain why a product has its priority and see whether advertising supported the decision?
Start with One Commercial Product
Retail catalogs contain several kinds of identity. A jacket may have many sizes and colors, each with its own offer ID in Merchant Center. Advertising and analytics may refer to those items differently again.
Expanly brings connected data into a product model and assigns one priority to each product for each scored day. Variant data can inform the decision, and eligible variant offers inherit it for Google delivery.
This avoids giving one commercial product conflicting priorities simply because one size has more history than another. It also gives the buying team a product it recognizes in the review.
The mapping still needs care. A product model must reflect meaningful commercial differences; it cannot be inferred safely from a shared name alone. Price differences between choices are one reason to review the grouping. The product workflow keeps the commercial decision connected to the underlying catalog.
See What the Growth Budget Supports
Campaign reporting tells the specialist how the account performed. A retail review also needs to show which products received the opportunity.
The shared view brings product advertising metrics together with the business fields connected by the retailer. A team can examine allocation by priority, inspect an important category and look for products that received little exposure despite the commercial plan.
The useful question becomes concrete: did the launch collection receive a fair test, or did spend continue to concentrate on established products?
This requires care with definitions. Google Ads conversion value and GA4 item revenue are different measurements. Expanly keeps them as separate measures rather than quietly combining them into a single sales number, and a review should say which one it is quoting. Product-level reports also have a different scope from account-wide campaign reporting.
The goal is a review the retailer can reconcile with its other systems. A bigger total is no help if nobody can explain it.
Define Priorities the Team Can Explain
Expanly uses High, Standard and Low as a shared commercial vocabulary. The retailer defines the conditions that produce those priorities.
A launch rule may require the right collection and sufficient availability. An inventory rule may combine stock cover with margin and evidence of demand. The right conditions depend on what the business is trying to achieve.
Rules have an explicit order. The first matching rule wins, and products matching no rule receive Standard. That gives the team a clear way to decide whether an availability guardrail should override a promotion.
It also exposes disagreements early. If the category team wants a scarce product supported while ecommerce wants to conserve stock, that trade-off should be resolved before the campaign result becomes the argument.
Once a workspace has its daily update time set, published rules are evaluated every day using connected data. They do not react instantly to every stock movement. Data freshness and missing fields remain part of the operating review.
Keep Experimentation Separate from Publication
A useful rule editor should let people explore. Changing a threshold to inspect its effect should not silently replace the logic used for live delivery.
Expanly separates draft configuration from the published baseline. Teams can inspect proposed rules and affected products before an authorized user publishes the approved changes.
After publication, daily evaluation can move products between priorities as their conditions change. That is the automation the team has agreed to. Changing the logic itself requires another explicit publication.
This distinction matters for accountability. Approving a launch rule means approving its guardrails and effective period, including the possibility that a product loses High priority when its availability falls.
A scheduled rule should be approved before its start date. The calendar determines when the approved logic applies; it does not approve a draft on the team's behalf.
Deliver the Signal Through the Existing Google Setup
The Google Merchant Center destination delivers a selected custom label through a supplemental data source. The retailer's primary feed remains responsible for the offer information.
The label gives the paid media specialist a business input. Google's custom-label guidance describes how advertiser-defined groups can support campaign organization and reporting. The agency still decides the campaign action, budgets and bidding.
A separate PMax asset group does not create a separate budget, and a High label does not instruct Google to spend a set amount. Teams need to agree what treatment the signal should receive and verify it in the account. The retailer–agency operating model covers that handoff.
The priority export can carry the business decision without exporting the detailed margin or stock data used to make it. The selected label slot should have a clear owner. Expanly's value takes precedence in that slot, so campaign filters that still depend on older values there would stop working.
Preserve the Date of the Decision
A product can be High for a launch and Standard a month later. Applying today's label to the earlier period would rewrite the story.
Expanly's scored history ties the product priority to the relevant day. That supports a review of allocation under the priorities recorded for those dates. A period before scoring began must remain distinguishable from a scored period.
Expanly can also score earlier dates with a workspace's approved rules, for example to give a new team a baseline. Those dates show what the rules would have selected. They are not a record of a priority that was live in the account at the time.
The history is an analytical starting point. It does not prove that Merchant Center and Google Ads used a new label at the exact moment it was published. Delivery evidence and campaign changes still matter, especially around the beginning of a test.
The same discipline applies to outcomes. If revenue rises after a rule change, the team should examine other changes in price, availability and demand. Our product-level reporting guide keeps those distinctions visible.
What Changes in the Weekly Trading Meeting
The model should make a familiar conversation easier to finish.
The category manager brings the commercial change. Ecommerce checks that the product data reflects it. The specialist explains how the account will use the priority. The team reviews affected products, publishes the agreed logic and comes back to the allocation evidence.
The first useful result may be an exception: a collection that never received meaningful exposure, an availability rule catching too much of the range, or a High cohort that expanded beyond its intended scope.
Those are decisions the team can act on. They are also much more useful than assuming that a campaign hitting its ROAS target means the retail plan was executed.
That is the standard we hold Expanly to: one product decision that people can define, follow into advertising and revisit with evidence.
