IndicaOnline Massachusetts A Guide to Catalog Mapping

image

A product catalog connects the object on a shelf to the rfile a cashier selects and the bundle stated to the kingdom. For an IndicaOnline Massachusetts implementation, mapping should always be deliberate: a transparent retail call is efficient, yet it can not change properly identifiers, devices, and product attributes.

Distinguish a product from a package

Use the product document for the retail id, including a model and % size. Keep kit-certain statistics tied to the precise stock won. Two batches of the identical product might also share a monitor identify whereas requiring separate kit references and scan expertise.

IndicaOnline describes stock synchronization in its Metrc integration documentation. Before allowing reside updates, ask which fields are imported, that are editable locally, and which variations are sent to come back. Do no longer count on that a exhibit-title edit is harmless in every integration.

Create a container-through-subject mapping sheet

    Record the resource subject, destination subject, and in charge files owner. Separate unit count number, internet weight, serving dimension, and package potency. Keep inside SKU, organization code, and country bundle identifiers varied. Document the approved type, tax therapy, and online display fields.

Specify how blanks and atypical values could be dealt with. A lacking potency magnitude should always cause assessment rather than default to 0. Preserve best zeros and complete identifiers while relocating info among approaches.

Validate models prior to importing at scale

For every single product category, paintings through a concrete example. A field of ten instruments will never be routinely ten retail packages, and milligrams of active aspect are not grams of product weight. Have the compliance lead approve any calculation used for purchase-prohibit equivalency.

Build a small look at various set protecting flower, concentrates, infused items, multipacks, and add-ons in which appropriate. Verify the package specific by means of the scanner, the quantity got rid of from stock, and the values shown on the receipt and on line menu.

Handle duplicates devoid of losing traceability

Do now not merge objects merely due to the fact their names seem same. Compare vendor, size, category, and the underlying kit relationships. Archive out of date monitor entries merely after confirming that historic transactions stay handy and associated to their original identifiers.

When seller naming differences, hinder an alias or cross-reference rather then rewriting history. Ask the seller tips on how to guard package deal links all the way through renaming and no matter if any update requires a controlled remapping manner.

Put catalog variations by way of review

Assign one character to advise differences and https://www.tool-bookmarks.win/massachusetts-cannabis-crm-consent-and-data-privacy some other to review sensitive fields. Save the previous cost, intent, productive date, and approval. After a bulk replace, pattern records from every affected class and compare POS, stock, and on-line output.

Maintain a brief exception queue for unmapped programs and conflicting attributes. Do not publish an merchandise until the guilty employee resolves the difficulty. Review new deliveries towards the mapping ideas so the catalog stays regular after onboarding.

A refreshing catalog makes receiving, checkout, and reporting easier to make sure. To see how it works, deliver genuinely anonymized product examples to an IndicaOnline demonstration and request a walkthrough from bundle intake to the final sales listing.