Skip to content
  • There are no suggestions because the search field is empty.

Retail | Company Products | Retailer Readiness Checklist: Moving to Company Products

The transition to the new BLAZE Company Products architecture marks a significant upgrade to how your inventory and data are managed. To ensure a seamless migration, it is vital to perform a data audit within your current BLAZE account. Completing these steps prevents duplicate entries, ensures pricing accuracy across all locations, and maintains the integrity of your global records.

Prerequisites

  • Access to the BLAZE Web Admin portal.

  • Administrative permissions for the designated Anchor Shop (the primary source for your global data).

  • A finalized list of active Vendors, Categories, and Products.

1. Data Integrity & Global Fields

The migration process utilizes your Anchor Shop as the primary source of truth. Please verify the following fields in your main location:

  1. Vendor Assignments: Every product must have at least one Vendor assigned. Products without an assigned Vendor will fail to migrate.

  2. Category Cleanup: Standardize your categories. If "Gummies" and "Gummy" both exist, they will be treated as separate categories. Consolidate these into a single name where possible.

  3. Brand Names: Audit for typos or variations in Brand/Supplier names.

  4. ASCII Characters Only: Remove special symbols or emojis from Product and Vendor names.

    NOTE: If the system detects special characters during migration, it will automatically replace them with an underscore (_).

2. Shop-Specific Information

The new architecture creates "Overrides" for any data that differs from the Anchor Shop. To minimize unnecessary overrides, audit the following:

  1. Pricing Audit: Confirm that location-specific pricing is intentional. If Shop B has a different price than the Anchor Shop, that difference will persist as a Price Override after migration.

  2. SKU Uniqueness: Every product should have a unique SKU. Resolve any conflicts where the same SKU is used for different products.

  3. Active/Inactive Status: Verify the status of your items; products marked as Inactive will remain Inactive in the new system.

3. Location Health (Required Fields)

The BLAZE sync engine requires specific contact data to generate your new Company profile. Ensure every location has the following fields completed under Settings > Shop Information:

  • Physical Address (Street, City, Zip)

  • State (Ensure the correct state is selected from the dropdown)

  • Shop Email

  • Phone Number

4. Advanced Features & Lab Results

If you utilize advanced inventory features, review these specific data points:

  1. Pricing Templates (PT): Ensure names and weight tolerances are consistent across locations. The migration will attempt to group these at the Company level.

  2. Lab Results: Verify that potency data (THC/CBD) is entered strictly as numerical values.

⚠️ What to Expect During Migration

Review the table below to understand how the system handles specific data scenarios during the transition:

Scenario Migration Action
Product Edits A "Read-Only" period may be enforced; do not edit products during the snapshot window.
Duplicate Names If two different products share the exact same name, the system appends _DUPLICATE to the name.
Milligram Units Products using "mg" will be converted to "grams" (e.g., 100mg → 0.1g) for global standardization.
Missing Vendors Migration will fail for that specific product record.