Merchandising

Merchandising is how your storefront sells: pulling the right products, reference material, and policy together to answer a buyer brief. It is the how of selling, distinct from a product, which is what gets sold. Your Merchandising Agent does the selling; merchandising is the configuration it sells by. Three Pages steer it. Each owns a different kind of fact, and all three are authored the same two ways — in chat with Murph, or in a portable Page you can open from any MCP Apps host. Per-buyer terms remain separate in buyer instructions and buyer discounts. A Product Marketing Media Kit can supply positioning, verticals, and other merchandising context. It is source material, not a structured configuration owner, and does not replace the Discovery Card’s coverage declaration.

​

One fact, one owner

Each fact has exactly one place it can be written. This is not a style preference — a Playbook instruction version that restates a structured price, a discount, a market, or an acceptance rule is rejected on save, and you are told which surface owns it. The reason is drift. Playbook instructions are prose your agent reads; Playbook pricing is structured data the pricing engine enforces. If a $25 floor lived in both, the two would eventually disagree and the agent would have to choose between them mid-negotiation. Instructions may refer to Playbook pricing, the Discovery Card, Product Marketing source material, or Business Rules — “lead with premium packages”, “follow the structured pricing” — but they may not restate their facts. If a rules version you saved earlier does contain such a fact, it stays readable and returns an ownershipIssues list naming the conflict. While that version is active, the conflicting lines are omitted from the copy your agent reads, and the structured surface stays authoritative. You cannot re-activate a flagged version; you save a cleaned-up one instead.

​

Versions and activation

Business Rules policy and Playbook instructions are versioned and immutable. Saving never overwrites: it appends a new version and points your storefront at it. Exactly one version is active at a time, and that is the one your Merchandising Agent reads on its next composition. A version that has been saved but not activated has no effect at all. Activation is what puts a document to work, so the ordinary path is save and activate in one step — your version history never contains a half-applied update. Earlier versions remain readable for audit, and the Page lets you preview one, restore it, or reuse it as the starting point for a new version. Playbook pricing and Business Rules approval gates are not versioned. A save takes effect immediately.

​

What changes when you save

Merchandising configuration is not inert — each surface changes what your storefront does on the next buyer request.

• Discovery Card changes the next Marketplace card and filtered storefront result. Its channels and accepted countries are declared coverage for a managed storefront; pass-through coverage remains upstream-owned.
• Playbook pricing changes the quote. Floors marked hard_floor are never crossed; a proposal composed after the save uses the new anchors.
• Playbook instructions change what gets offered and how it is described. The active version is read on the next composition.
• Business Rules policy changes which briefs are eligible. Every managed storefront applies it during product discovery. Manual media-buy approval evaluates the submitted buy again before Approval Mechanics. Clearly on-policy buys auto-forward; ambiguous results, evaluator errors, and deterministic hard findings enter the human queue before any source write.
• Business Rules approval gates change which work needs human review. With mediaBuyApproval: manual, clearly on-policy buys auto-forward and exceptions queue; with auto, create_media_buy preserves the established auto-forward contract after the buyer has passed product discovery.

​

Reading your current configuration

Every surface is readable before and after you change it:

• Ask Murph, or open the surface’s Page, to see the current document.
• GET /api/v2/storefront returns compositionPricing, creativeApproval, and mediaBuyApproval.
• The acceptance-policy and operating-instructions endpoints return the active version, the full version history, and each version’s ownershipIssues.

​

Next steps