Completing this task requires early access to Lightspeed
Which will be emailed to you 2-3 weeks before Go Live. Click here for more details
This article will guide you on how to use your early access to Lightspeed to review and update the products migrated from NetSuite into your new Lightspeed instance.
Overview
2-3 weeks before Go Live | Up to 1 day before Go Live | Go Live |
---|---|---|
Product migration from NetSuite | Lightspeed product review & updating | Stock quantity migration |
The Evolution Team will snapshot your product data (excluding stock) from NetSuite, transform it, and import it into Lightspeed. Notes:
| You will review and update the migrated products in Lightspeed. Details on how to complete this are below. | After 5pm the night before Go Live, your NetSuite stock quantities will be loaded into Lightspeed as a PO for review on the day of Go Live. Further details on this step are covered in the migration checklist. |
Product Migration Report
In your "FP Shared" Google Drive folder, you'll find reports detailing the outcome of the migration of your NetSuite products to Lightspeed. The link to this folder can be found in the "Overview" tab of your migration checklist.
Critical Action to Avoid:
Do not edit product details in the report. Use it only as a reference and make all updates directly in LightSpeed.
Steps to Review and Update Products
Essential Actions to Perform:
Prioritise key products needed for the first days of trading at go-live. You can continue updating Lightspeed after Go Live.
Step 1: Review and Validate Migrated Products
In your "FP Shared" folder open the spreadsheet called "LS Std and Local Products." This contains two main sheets: LS Standard Products and LS Local Products.
Standard Products Sheet
Critical Action to Avoid:
Do not change the product category or remove tags of standard products. These are critical for reporting and PSC product updates. You may add additional tags.
Do not delete standard products.
- Validate local product Mappings: Check that they have been mapped to the correct standard product/s.
- Mapped Product details: Columns AK, AN and AO show the mapped Internal ID, Sales, and Purchase Name of the NetSuite local product.
- If incorrectly mapped, replace the 'Mapped NS Internal ID' column with the correct Internal ID only.
- If no mapping exists, enter the relevant NS Internal ID into the 'Mapped NS Internal ID' column.
- Impact of Mapped IDs: The mapped NS Internal is essential for stock migration the night before go-live. The mapped product will be removed from LightSpeed.
- Mapped Product details: Columns AK, AN and AO show the mapped Internal ID, Sales, and Purchase Name of the NetSuite local product.
- Purchase Price Validation: Ensure the purchase price aligns with the sale unit and price. Mistakes here impact COGS and are difficult to correct once trading starts.
- Review Orange Highlights: These indicate products that couldn't be mapped to a local product, leaving no sales price. Enter the local NS internal ID in column AK and use the Edit Product link in column AQ to update these prices directly in LightSpeed.
- Inactivae Standard Products: For standard prodyct not used in your business, use the Edit Product Link in column AQ to deselect 'Sell on point-of-sale' to inactivate them.
Local Products Sheet:
- Identify products to be removed from the catalog.
- In LightSpeed, remove tags from the product
- Add a tag ‘Delete’.
- These products will be deleted the night before go-live.
- Note: This action can only be performed on local products. Standard products must remain in the system but can be made inactive.
- Ensure the purchase price aligns with the sale unit and price. Mistakes here impact COGS and are difficult to correct once trading starts.
Additional Reference Sheets:
- NS Products Sheet: Displays what was exported from NetSuite and how it maps to LightSpeed products. This sheet also lists products that couldn't be imported from your local list.
- LS PO Stock: Offers a preview of stock mapping. If you find discrepancies, refer to the process under the Standard Product Sheet section so the stock migration can be updated accordingly.
Step 2: Add additional products
- Add any missing products to LightSpeed using the naming convention ‘[Brand] [Product Name] - [Size]’and assign a product category.
- Use the ‘Duplicate Products’ file to reference products that couldn’t be uploaded due to duplicate SKUs or names. Add these products directly in LightSpeed, ensuring unique names and SKUs.
- Add composite or variants products necessary for immediate trading. Less frequently ones can be added later.