# Managing QR, print, direct mail and proof

Availability: Planned API.
Last reviewed: 2026-08-28.

Prepare trackable physical collateral and retain evidence of what happened to it. The planned outcome links QR identity, design approval, print/mail orders and proof.

## Design the artifact

Provide the campaign or Store reference, approved creative/media, destination intent, physical format, quantity and delivery scope. A QR code has a durable identity and versioned destination; a changed destination must not erase prior scan context.

Print-ready output and a rendered preview are design artifacts, not manufactured goods.

## Place work explicitly

A reviewed print or direct-mail request needs recipient/address scope, rights, cost and approval. Provider acceptance, production, shipment and delivery remain distinct stages. Do not infer them from a successful export.

For example, an approved postcard design may exist while its order is unfunded and no mail has been submitted.

## Read evidence carefully

A QR scan is an engagement event, not a sale. Submitted placement or fulfillment proof requires the appropriate review before acceptance. Accepted proof does not automatically mean credits were consumed, earnings settled or an operator paid.

## Availability

Business APIs are planned. Raw provider fulfillment, financial attestation overrides and arbitrary mail submission remain excluded. Customer outputs are governed assets, order/status records and permitted evidence, with privacy and retention appropriate to the recipients.