Run a product label pilot

1. Prepare the manufacturer trial

Complete your organization and product catalog, then confirm the permanent public HTTPS domain before printing. Product QR codes remain independent of campaign dates. Do not issue localhost or temporary preview URLs on real product stock.

1. Create or enrich the product and add any batch/lot entries.
2. Generate the permanent QR and confirm its product and lot on the public form.
3. Ask your operator to run deployment readiness and anonymous smoke checks.

2. Choose staff email notifications

Open Settings and choose active staff recipients for positive feedback, suggestions and complaints. Organization administration and member-directory permissions are required. Recipients keep their existing branch and department restrictions.

Emails contain a sign-in link without customer comments, photos or contact details. Production outbox delivery runs through Celery and its one-minute dispatcher. SMTP acceptance is not proof of inbox delivery; confirm receipt with your actual mail provider. Synthetic demo workspaces cannot send email.

3. Print mixed products and batches

In Print Studio choose A4 mixed product / batch sheet. Add each permanent QR and its quantity. The same label geometry applies throughout the sheet; quantities must fit the displayed capacity. Unused cells remain blank.

Mixed sheets require organization-wide QR permissions. Each printed code keeps its own product and lot. QR codes are not copied onto another product or converted into expiring campaign codes.

1. Save the design and review the accurate preview and module size.
2. Download the vector PDF or SVG and the blank sticker test checklist.
3. Print at 100 percent / actual size and measure the supplied 20 mm reference bar.

4. Record an actual physical scan test

Automated geometry and PDF barcode decoding cannot validate your printer, adhesive, bottle curvature, lighting or camera. Fill in the blank printable record rather than treating an automated pass as physical approval.

1. Print on the actual intended stock and apply a sample without covering original product/lot/safety information.
2. Try signed-out iPhone and Android camera apps under representative conditions.
3. Confirm HTTPS, readable fallback, correct product and batch, anonymous submission and staff notification.
4. Record devices, printer, measurements, failures and evidence before approving the trial.

5. Read the pilot dashboard

Reports includes Manufacturer pilot dashboard when you have product-view and feedback-analytics permissions. Filter by product, batch and period to see recorded QR resolver requests, submissions, positive reviews, suggestions and customer-classified quality complaints.

Scan counts include repeated requests and bots; they are not unique people or proof that a camera scanned a physical label. Positive reviews include permitted private records, while public publication still needs separate customer consent and moderation.

6. Keep demonstrations separate

The development-only Medipharm scenario is explicitly synthetic and unaffiliated. Fictional products, batches, scans and responses are isolated in a marked demo organization. No real logo, manufacturing specification, contact list or endorsement is used.

The ACK Lysing Buffer demonstration is also marked as a demo. Obtain authorization and use actual deployment settings before any real manufacturer trial.