GETTING STARTED · PREPARATION ORGANIZATION
From agreement to a ready store.
One plan, clear responsibilities.
The web store preparation plan connects materials, settings, and checks in an actionable sequence. Its purpose is to ensure that both your team and Connect know what needs to be done, who is responsible, and when the task is truly complete.
Adapt the plan to the actual scope of the project. A store with a smaller catalog and standard delivery will not have the same tasks as a multilingual B2B store with business system integration.
Go through the guide
First, agree on the initial scope
Determine which products, markets, languages, payment methods, and delivery methods you are starting with. Distinguish what is necessary for the initial launch from improvements that can come later.
Write down special requirements before setup: selling to business customers, working with variants, reservations, or connecting to an ERP system, if they are part of the project. For each additional capability, confirm its availability and scope with the Connect team.
Organize the preparation into five phases
1. Materials and access
Collect business data, the catalog, and visual materials, and confirm the people and accounts for administration.
2. Store and catalog
Organize the brand presentation, offer structure, and initial product selection.
3. Payments and fulfillment
Align payments, delivery areas, costs, time frames, and information for customers.
4. Testing and corrections
Check the customer-facing view, test order, and processing. Record and check corrections again.
5. Launch confirmation
Check the team's readiness, agree on the launch, and define how the first orders will be monitored.
Define what completion means for each task
The task “prepare products” is too broad for reliable tracking. Divide it into specific steps, such as submitting photos for the initial assortment, checking prices, and confirming availability.
For each task, record the responsible person, agreed deadline, and status. Add what the task is waiting for: materials, access, a decision, or a check. Use one agreed record so everyone is looking at the current version.
- Task: prepare photos for 20 initial items.
- Responsible person: a designated person from your team.
- Expected result: photos labeled with item codes and submitted through the agreed channel.
- Check: confirmed that each selected item has a suitable photo.
Account for dependencies and decisions that can stop work
Product entry depends on ready data. Payment testing depends on a configured payment method. Delivery checks depend on agreed areas and prices. Take these links into account before setting deadlines.
If the scope changes, record what was added and check the impact on costs, responsibilities, and timing. Align new requirements before implementation instead of silently adding them to the existing plan.
Finish with a readiness check, not just a list of entered data
Preparation is complete when the data has been checked, purchasing and processing have been tested, and the team knows what to do after a new order. Sort open issues into those that block sales and improvements for later.
Agree on who gives the final confirmation, when the store launches, and who monitors the first orders. Keep a record of the remaining tasks after launch.
Frequently asked questions
Is there the same preparation deadline for all stores?
No. The deadline depends on the agreed scope, data readiness, required integrations, and checks. Agree on a specific plan for your store.
Can we add part of the offer after launch?
Yes, if you agree on this as part of the initial scope. Before launch, you should confirm that the offer you are starting with is complete and ready for sale.
