Retail | Company Products | Migration & Auto-Onboarding

The Transition to Company Products

We are upgrading all accounts to a new Company Products infrastructure, moving from a shop-centric model to a unified global "Company" model. This transition standardizes your inventory architecture across all locations, replacing legacy management pages with a centralized ecosystem. Once migrated, you will gain access to a "tree-style" Category Hierarchy for parent/subcategory relationships, unified management for Brands and Vendors, and a global Stock column that aggregates inventory across all shops with a detailed hover-over breakdown per location.

Important Migration Details

Please note that this is a "one-way door" migration; once your account is upgraded, legacy shop-centric management will no longer be available. To ensure a seamless data transfer, there will be a brief read-only period during your scheduled migration date where product edits should be avoided. During this process, the system will automatically deduplicate identical items across shops to create a clean master list. Additionally, any products currently measured in milligrams (mg) will be automatically converted to grams (g) (e.g., 100mg becomes 0.1g) to align with new global reporting standards.

Prerequisites

• Vendor Assignments: Every product must have at least one Vendor assigned; missing vendors will cause migration failure.

• Location Health: All shops must have a valid Physical Address, State, and Email populated.

• Data Standardization: Clean up Categories and Brands to prevent duplicate global entries (e.g., merging "Gummy" and "Gummies").

• ASCII Compliance: Remove special characters or emojis from Product and Vendor names (the system will replace these with underscores if found).

Core Principles: 

1. Internal Only: Only users with isBlazeAdmin credentials can access this page.
2. Deduplication First: The system identifies products across different shops that are actually the same item (using Dedupe Keys like Name + Brand + Category) to create one single Company Product.
3. Safety First: Before any data is moved, the system creates an S3 snapshot of the original shop data.

Internal Auto-Onboarding Steps (Admin Only)

1. Navigate to Global Settings > Development Tab and select Enable Company Products.
   

2. Select the target company and click the blue cloud icon to generate/download a data snapshot.
   

3. In the Channels menu, select Company and add shops to the dropdown.

   IMPORTANT: The order of selection matters. The first shop selected acts as the Anchor Shop (Source of Truth) for global values like images and descriptions. Shop Overrides: If Shop B has a different price than the Anchor Shop, the system automatically creates a Price Override for Shop B during the migration.

4. Select Brands, Vendors, Pricing Templates, and Categories, then click Export > Export Missing Collections.
   

5. Once the export status is confirmed, click Import and wait for the "Completed" status.
   
   
   

6. Select the Refresh Button to see the status > refresh until you see the completed status.
   

7. Select Migrate Products and execute the following in order:

8. Pre-Validation & Cleanup

   • Disable Events: Toggle this to prevent feedback loops during the heavy data load.
     
     

   • Pre-validation: Run this to identify name collisions within shops.  This step will check to see if you have any duplicated products based on the requirements for the duplicate keys that you set. If you do have duplicated products, an error message will appear that tells you the name of the product, the shop names, shop ids, and the product ids of the duplicated products.
     

   • Fix Duplicates: Use the Fix Automatically button to prepend "DUPLICATE" to problematic names.

   • Validate & Deduplicate: An important step when you have products in multiple shops, it will remove duplicates and ensure that your data aligns with the original exports you conducted earlier.

   • Create Products: Generates the entries in the Company Products infrastructure.

   • Validate Migration: this step will verify that the Company has all of the expected data (such as prices, brands, vendors, etc.) based on your original product export.

   • Update Platform IDs: Assigns IDs to link the US Monolith to the new framework.

   • Sync Open Search: Finalizes searchability (Skip for staging environments).

Important Notes: 

• Any new shop created after onboarding will now automatically receive the Company Products catalog
• Special Character Handling: The system now automatically replaces non-ASCII characters in names with underscores (_) to prevent ingestion failures
• Unit Conversion: Automatically handles "mg to g" conversions (e.g., a 100mg product is correctly migrated as 0.1g).
  
  

What to Expect Post-Migration

• Read-Only Snapshot: During the migration, product edits should be paused to ensure data integrity.

• Automated Cleanup: Identical items across shops are deduplicated. Conflicting names in the same shop will have _DUPLICATE appended.

• Aggregate Stock: A new Stock column in the dashboard displays total inventory across all locations with a hover-over breakdown.

Troubleshooting & Safety Controls

• Status Polling: The migration runs on a background EC2 server; you do not need to keep the browser window open.

• Error Handling: If a batch fails, use the Download Error File button to view a CSV of specific row failures (e.g., "Invalid SKU").

• Rollback: In the event of a catastrophic failure, use the Clear DynamoDB button to wipe the migration state and restart the process.

• Redundant Overrides: Remind users that if a shop-level value matches the company default, the system will automatically remove the redundant override.
• Case Sensitivity: New logic prevents duplicate vendors/brands caused by capitalization (e.g., "Acme" vs "ACME").
• Wait Times: For large datasets (10k+ rows), inform the team that the EC2 task runs in the background and they do not need to keep the browser window open.

Retailer Readiness Checklist: Moving to Company Products

To ensure a smooth transition to our new Company Products architecture, please review and complete the following steps within your current BLAZE account. Cleaning your data now prevents duplicate entries and ensures your pricing remains accurate across all locations.

1. Data Integrity & Global Fields

The migration uses your "Anchor Shop" as the primary source for global info. Ensure these fields are accurate in your main location:

• [ ] Vendor Assignments: Every product must have at least one Vendor assigned. Products without Vendors will fail to migrate.
• [ ] Category Cleanup: Ensure your Categories are standardized. If "Gummies" and "Gummy" both exist, they will be treated as two different categories.
• [ ] Brand Names: Check for typos in Brand/Supplier names.
• [ ] ASCII Characters Only: Ensure Product and Vendor names do not contain special symbols or emojis. (The system will replace these with underscores _ if found).

2. Shop-Specific Information

The system automatically creates "Overrides" for any data that differs from your Anchor Shop.

• [ ] Pricing Audit: Confirm that any location-specific pricing is intentional. If Shop B has a different price than the Anchor Shop, it will remain different after migration via a "Price Override."
• [ ] SKU Uniqueness: Every product should have a unique SKU. If you use the same SKU for different products, please resolve those conflicts now.
• [ ] Active/Inactive Status: If a product is "Inactive" in your current shop, it will be migrated as "Inactive" in the new system.

3. Location Health (Required Fields)

Our sync engine requires specific contact data to create your new Company profile. Ensure every location has the following filled out:

• [ ] Physical Address (Street, City, Zip)
• [ ] State (Ensure this is correctly selected)
• [ ] Shop Email
• [ ] Phone Number

4. Advanced Features (If Applicable)

• [ ] Pricing Templates (PT): If you use Pricing Templates, ensure the names and weight tolerances are consistent. The migration will attempt to group these at the Company level.
• [ ] Lab Results: If you have potency data (THC/CBD), ensure the values are entered as numbers.

⚠️ What to Expect During Migration

1. Read-Only Period: Your BLAZE Admin may ask you to refrain from making product edits for a short window while the "Snapshot" is taken.
2. Automatic Renaming: If the system finds two different products with the exact same name in one shop, it will automatically append _DUPLICATE to the name to allow the migration to proceed.
3. Milligram Conversion: Any products currently using "mg" as a unit of measure will be converted to "grams" (e.g., 100mg → 0.1g) to align with global standards.