Bulk product copy: test first, then check every result

Look at the products before the file format

A spreadsheet helps you review a product list, but each store platform structures its fields differently, so the data does not carry over unchanged. Option structure, images and category placement can all differ in the target store. Whether you move products with a file or copy them with COZi, check these yourself.

• Include products with the option combinations you really sell in your test.
• Open copied products and check that the main, additional and description images display.
• Decide which category each product belongs in before the bulk job.
• Mark the products that already exist in the target store, including your test copies.

Choose the source and target store in COZi and read the preview. A successful test does not mean every other product will copy the same way, because each product has its own options and images.

Follow a started copy on the job screen

A bulk copy that has started runs as a job on the COZi server. You can leave the screen and open the same job again later, so closing a tab is no reason to start a new copy.

Write down the scope and the target store so a colleague can take over. Processing speed depends on product structure and the store platform, so plan around actual results rather than an estimated finish time.

• Read the job status and decide whether to wait or act.
• Compare the number of products processed with the number remaining.
• Read the failure and skip reasons for each product, not just the progress bar.
• Keep a note that identifies the job, plus a list of products to handle by hand.

Check the results after a pause, resume or cancel

Bulk jobs support pause, resume and cancel. A pause takes effect after the product in progress finishes, and products already created stay in the target store when you cancel.

• Pause. After pressing it, check that the status changes to Paused.
• Resume. Check the target store and the remaining scope, then continue the job.
• Cancel. Use it when you do not want the remaining products processed. Afterwards, check the products already created in the target store.

What to check on each copied product

Which fields move depends on the source and target store combination. Check the finished page of a few representative products, and keep a separate list of the products the preview marks as not copyable.

• Before the main job, check category placement and the settings the target store needs.
• Compare option choices, extra prices and availability with the source.
• Open images and descriptions, and look for links that still point to the source store.
• For each skipped or failed product, decide whether to fix a setting, retry or list it by hand.

Avoid creating the same product twice

By default, a bulk copy skips products that were already copied and marks them as already copied. It still helps to separate test copies, products already in the target store and products not yet moved. Remember that a copy creates a new product; it does not update an existing one.

• Leave test copies out of the main scope, or mark them.
• Check earlier job results before copying the same product again.
• If COZi could not confirm whether a product was created, check the target store before retrying.

Leave time for review and exceptions

Processing speed depends on the products and the store platform. Image count, option structure, platform rate limits and temporary connection problems all affect it. Even if the service shows an estimated time, do not use it to set your launch time.

After processing finishes, you still need time to review products and sort out failures. Put that time in your plan before you announce a launch date to customers.

What to check in the preparation summary

A bulk copy checks the selected scope first, then asks whether to start. Read the summary and fix any settings that block the job. How you choose the scope, the limits and the required fields differ by store combination.

• Scope. Confirm the source store, the target store and the products included by your selection or filters.
• Copy eligibility. Check which products will be copied, which will be skipped and why.
• Execution requirements. Check connected account permissions and the target store’s listing requirements. Test with a few products and review the results before expanding the scope.
• Target store settings. Finish required settings such as categories. With an Imweb target store, choose a fallback category for products that have no category with the same name.
• Fresh data. If you recently changed products in the source store, import them again before preparing the job.

How to run a bulk copy

1. 1

   Import fresh products and test

   Import your product list again and copy a few representative products first.

2. 2

   Choose the remaining scope

   Open bulk copy and choose the rest of the scope. Check that it does not overlap your test copies.

3. 3

   Read the preparation result

   Before starting, check the product count, the products to be skipped, and the required settings and notes.

4. 4

   Start the copy

   Confirm the target store and selected products, then start the copy.

5. 5

   Follow progress

   Watch progress and per-product results on the job screen, and pause or cancel if needed.

6. 6

   Handle exceptions

   Read the failure and skip reasons and fix the causes. Retry the products that can be retried, and list the ones that cannot be copied by hand.

Start with a small scope in COZi. If bulk copy is not available for your combination, use selected-product copy, or check whether full-store registration in the COZi console can list one store's products in another store as new products.