Hosting and technical capacity
Estimate catalogue size, imports, traffic patterns, media, search, payment and shipping integrations before selecting hosting. Record who owns staging, backups, monitoring and recovery.
Catalogue model before import
Define product types, variants, attributes, stock rules, tax and shipping inputs before preparing data. A clean source sheet prevents repeated manual repair after launch.
Extension and licence ownership
List every required payment, shipping, subscription, multilingual or operational extension. The written scope identifies who purchases, renews and receives administrator access.
Search and conversion structure
Plan categories, product URLs, filter behaviour, canonicals, metadata, structured data, product evidence and internal links as one store architecture—not an SEO patch after upload.
Operational handover
Confirm order roles, notifications, refunds, customer exports, content editing and maintenance responsibility. Client-approved security, privacy and compliance requirements remain part of the operating brief.
Platform scope questions
Can WooCommerce support a large catalogue?
It can support different catalogue sizes, but hosting, database activity, search, imports, extensions, media and traffic must be evaluated together. The written scope confirms the tested assumptions rather than promising a universal product limit.
Who owns the hosting and WooCommerce extensions?
The client should retain ownership of the hosting and paid extension accounts used for the store. The proposal records who purchases each item, which renewals are separate and what access Agal needs for delivery.
Are product copy and image preparation included?
Only when they are listed in the written scope. The base build can use accurate source material supplied by the client; writing, image cleanup, bulk data repair and custom artwork are separate deliverables when required.