Create or update the link between one of your Distru products and its matching product in a single external POS catalog (Blaze, Dutchie, or Treez). This link is what lets Distru recognize the same product on both sides when it reconciles catalogs, menus, and inventory with that retailer, so mapping a product is a prerequisite for that retailer's POS integration to act on it.

You do not send a POS type. It is derived from which POS fields you supply, and you must supply exactly one complete pair: • Blaze: blaze_product_id + blaze_retailer_id (optionally blaze_asset_id). • Dutchie: dutchie_product_id + dutchie_retailer_id. • Treez: treez_product_id + treez_retailer_id (optionally treez_photo_url).

Supplying no complete pair, or fields belonging to more than one POS, returns 400 — a mapping targets one POS only.

Create vs. update is decided for you: the request matches an existing mapping by product plus the retailer of the supplied POS. A match is updated in place and returns 200; no match creates a new mapping and returns 201. Because the match key is stable, sending the same body twice is idempotent and never produces a duplicate.

Before the mapping is written, several things are checked and any failure returns 400 with a human-readable message: • The product_id must be a product in your company. • The supplied retailer must be a POS retailer connected to your company. • The supplied POS product must already exist in Distru's synced copy of that retailer's catalog — you cannot map to a product Distru has not yet pulled from the POS. • For Blaze only, the product's category must already have a Blaze category mapping configured for that retailer.

Uniqueness is enforced on both sides: a given POS product can back only one Distru product per retailer, and a Distru product can have only one mapping per retailer. Violating either returns 400.

On update, only the fields you send are changed — the request is sparse. The product_id plus the complete POS pair must always be present (they form the match key and are re-validated), but the optional fields are treated per-field: omit blaze_asset_id or treez_photo_url to keep its current value, or send it as null to clear it. Repointing to a different POS product for the same retailer is a normal update: send the new ..._product_id with the same product_id and retailer id.

This endpoint only maintains the link record — it does not itself move inventory or push the product to the POS; it makes the product eligible for that retailer's sync.

Required permission: products_permissions_edit.

{
  "blaze_product_id": "blaze_123",
  "blaze_retailer_id": "456e7890-e89b-12d3-a456-426614174000",
  "product_id": "123e4567-e89b-12d3-a456-426614174000"
}