Your store. Your catalog. One place to operate.

Start with a representative group of products rather than your entire inventory. Include a simple product, a longer description, a product with several images and an item that should remain unpublished. This makes it easier to identify formatting or data problems before expanding the catalog. Give each item a stable identifier so future imports can be compared against the same product rather than treated as unrelated additions.

Review the import proposal row by row where needed. An accepted file does not mean every value matches your commercial intent. Confirm which products are added, which are updated and whether an existing item should keep its current status.

• Check identifiers, names and descriptions against your source.
• Verify prices and currency before confirming the batch.
• Inspect the resulting records after applying the changes.

Use images you own or have permission to publish. The managed image pipeline optimizes assets before they can be used on managed pages; do not treat a pasted external URL as proof that an image is ready. Check that the finished asset loads in the draft and that the crop still communicates the product clearly on a narrow screen.

Search metadata should describe the actual item and match the visible page. Write specific titles and useful descriptions instead of repeating a list of keywords. Keep product descriptions readable for a customer who has not seen the product before. Image optimization supports delivery efficiency; it is not a guarantee of search rankings.

• Open the draft on desktop and mobile.
• Check image loading and product identification.
• Keep SEO text consistent with the visible offer.

A shared catalog is appropriate when two compatible storefronts should present the same business facts. It is not a shortcut for grouping unrelated sellers. Review the source business, the target website and the affected drafts before confirming a connection. Local page content can remain distinct even when products and identity come from a common source.

A connection also changes the scope of future edits. Someone maintaining a product needs to know that its description may appear in more than one draft. The current managed workflow bounds catalogs at 500 items and a shared source at 20 websites. Evaluate those limits against the size of your operation before planning a migration.

• Confirm that the sites represent the intended business.
• Tell editors which drafts share the source.
• Keep separate businesses on separate sources.

A good-looking product page does not prove that a customer can complete the intended purchase. Catalog facts, inventory, orders and payment configuration are separate concerns. Connecting websites to a shared catalog does not merge their stock, order history or checkout settings. Review the actual checkout mode and connected providers for each website.

Distinguish a manual order workflow from a connected payment flow. A submitted order or an assistant's message is not evidence that a payment settled. Test the path appropriate to your configuration and inspect its resulting order or provider status. Do not migrate an existing store solely on the basis of a storefront preview.

• Verify the website-specific purchase path.
• Check the expected order and payment outcomes.
• Confirm who handles exceptions and customer questions.

Before publishing, ask someone other than the content editor to read the store as a customer. Check the business name, contact details, public product status and any customer-facing policy links. Verify that the intended address serves the reviewed website, rather than assuming that creating a draft also provisions a live domain.

After publication, open the public URL independently and inspect the result again. Keep a record of who controls the domain, where DNS changes are managed and how the business can obtain its catalog or site data. A managed service should have a clear operating arrangement as well as a polished storefront.

• Publish only the reviewed website and revision.
• Verify the public URL, links and images.
• Document domain access and data handoff expectations.