Partner offer rules in an Uzbekistan shared catalogue
Keep source observations, merchant offer instructions and partner product selections separate when preparing a shared-catalogue data brief.
A shared product record can support several partner stores. A useful handoff distinguishes observed product data, the merchant’s offer instructions and the products selected for each recipient.
Developer Valery Danyuk describes a shared catalogue with store-specific markups in his Savdogarlar account for Uzbekistan. This external account supplies context for the editorial method below.
Keep a source price attached to its source
A collected price needs context before anyone uses it in an offer. Keep the source link, source item and variant, observed amount, currency, selling unit, quantity condition and collection time together. A price for a carton and a price for one piece should remain distinguishable after the records reach a shared catalogue.
Give the observed amount its own field. If someone converts the currency or applies a markup, retain that as a separate calculation with its input reference. Replacing the collected amount with the selling amount removes the basis needed to explain a later difference. A new collection can then update the observation without silently rewriting an approved commercial rule.
Attach the offer rule to the relevant partner
A partner-specific offer can reference the shared product record while carrying its own price rule, rounding instruction and review status. Record who supplied the rule and which version the recipient should use. Ask whether the calculation is a markup on cost or a target margin; those instructions produce different amounts.
Use an explicit status when the instruction is missing. An empty markup must not automatically become zero, and an old rule must not gain a new approval merely because fresh product data arrived. The merchant responsible for the offer should decide how unresolved records are handled before publication.
Review catalogue membership separately
A product can exist in a shared catalogue without belonging in every partner's export. For a proposed handoff, agree a product-to-partner list or a category-selection rule, then review a sample of the resulting rows. Include an item that should be included and one that should be excluded.
If the recipient needs a distinction between internal and partner-visible fields, make that an explicit requirement. A catalogue relationship by itself does not establish permission to disclose a supplier cost. Visibility rules belong in the agreed scope, with the responsible reviewer named.
Test a changed record before accepting the file
Use a fictional product to trace one change through the handoff. Change the source amount while leaving the partner rule fixed, then check the resulting offer against the agreed calculation. Next change the selling unit, or remove the product from one partner's selection. The reviewer should be able to identify the affected rows and the decision required.
File acceptance can confirm that the agreed fields and calculation examples are present. A recipient still needs to confirm its import result and any subsequent publication. Keep those acceptance steps distinct so a correctly prepared file does not become an unsupported claim that every partner has updated its store.
Discuss a representative sample
For a PandaBuyNow project discussion, bring representative source links, one target file and the merchant's intended offer rules. Identify the source facts to collect, the commercial instructions to preserve and the questions a reviewer must resolve.