Medicine facts, Product Policy & SKU approval
Record label facts separately from sale policy and obtain shop-pharmacist approval per version.
On this page · Jump to a section
Before you begin
Clear SKU/variant/pack identity with label and provenance a responsible reviewer can verify.
Where to go
Products → Pharmacy Protocols → Product Policy
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- Create products/packs from the physical item. Record active ingredient, strength and dosage form only as label facts; blank means unknown, never memory-filled.
- Create Product Policy with product type, regulatory framework, sale policy, quantity limit and reviewed source, then submit DRAFT to PENDING_REVIEW.
- Master/barcode data is only a suggestion. Applying it copies a shop-owned DRAFT snapshot; it never approves or silently replaces policy.
- A licensed pharmacist reviews SKU, size and evidence, then approves or returns it. Editing an approved policy requires a fresh review cycle.
- Review missing/pending/approved policy counts before opening. Choose whether backlog blocks shift open or uses counter authorization under shop settings.
How to verify success
Every sold SKU has readable status/provenance, strength/unit identity is correct and edited policy does not remain APPROVED.
Limits & things to check
Product Policy approval governs sale rules only; it does not approve indications, directions, safety wording or patient suitability.
Ready to try it in your shop
Lessons are free to read. Actual operations require sign-in and the appropriate permission. Use test data for training.