An ecommerce website quote is more than a build price: it should show what will be designed, configured, supplied and supported, and what remains your responsibility. Two proposals can use the same platform yet cover very different work, from product loading and payment setup to shipping rules, data migration and testing. Comparing only the headline figure can leave you exposed to extra fees, delays or a store that does not fit how you sell. Use this checklist to compare like with like. Start by separating one-off design and development from recurring hosting, maintenance, software subscriptions and payment-provider charges. Then check the number and type of pages, products, payment and delivery options, integrations, content and launch support included. Ask each provider to identify assumptions, exclusions, dependencies and the process for approving changes before work begins. Your best-fit quote is not automatically the cheapest or the most feature-packed. It is the one that clearly connects the store you need now with a practical way to operate and extend it later. The sections below help you ask specific questions and judge the trade-offs without assuming every store needs the same setup.
Content
Check the project scope
Turn the quote into a deliverables checklist
An ecommerce quote is only useful to compare when you know what work sits behind the total. Ask each provider to describe the same stages, from initial discovery through to launch and handover. A low price may reflect a smaller scope, while a higher one may include work you do not need. Neither is automatically better: the important thing is to understand what you are paying for and what remains your responsibility.
For discovery, check whether the provider will discuss your customers, catalogue, fulfilment process and business requirements, and whether this is included in the fee. For design, clarify whether the quote covers a store-specific design, use of an existing theme, or both options for you to choose from. Ask how many key page layouts are included and whether the design will be reviewed with you before development begins. A quote that says only “website design” leaves too much open to interpretation.
For development, look for a clear description of the work: for example, setting up the agreed store structure and building the pages and functions listed in the proposal. Check whether any required integrations or configuration are included, or whether they are still to be assessed. The quote should also state how revisions work. Find out how many review rounds are allowed, what counts as a revision, and how additional requests will be priced or approved. This helps distinguish normal feedback on agreed work from a change in scope.
Agree who supplies what
Content and product information can take significant time to prepare, so make responsibilities explicit before accepting a quote. Ask who will write or edit page copy, source images, prepare product descriptions, and provide details such as prices, stock information, dimensions, options and shipping weights. Confirm whether the provider will enter supplied information into the store, and, if so, what quantity or format is included. If you are supplying the material, ask when it is due and what happens if it arrives late or needs substantial correction.
Also check what the quoted design work assumes about your brand assets. If you need to provide a logo, product photography or other materials, list them as your tasks. Do not assume that “content included” means product copywriting, photography and data entry are all covered; ask for each item to be named in the scope. Where information is not ready, agree whether the provider can use clearly identified placeholders during development and how final content will be added.
Before launch, ask what testing is included and who signs off that the agreed pages and purchasing steps are ready. Clarify whether the provider will help with launch-day checks, connect the finished store to your domain, or assist with moving it from a development environment. Finally, request a handover list. This may identify what access, documentation or training is included, who receives administrator accounts, and what support is available after launch. Check whether ongoing maintenance or hosting is part of this proposal or needs a separate agreement.
A practical way to compare proposals is to put each stage in a simple table and mark it as included, excluded, or needing clarification. Send the same questions to every provider and ask them to update the quote where assumptions are unclear. Keep a written record of agreed deliverables, your own tasks, review limits and any items that will be quoted separately. That gives you a more reliable basis for comparing project costs than the headline figures alone.
Compare store features
Map store features to the way you sell
A quote can sound more comprehensive simply because it lists more ecommerce features. Before comparing those lists, write down how customers buy from you now and what the store must support at launch. Ask each provider to identify which requested features are included, which are optional, and which are excluded. This helps distinguish useful functionality from complexity that adds setup, testing or ongoing costs without meeting a current need.
Start with the catalogue. Check whether the proposal allows for your product types, options and variations, such as different sizes or colours, and whether customers need to filter or search a large range. If you sell a small number of straightforward products, you may not need an elaborate catalogue structure. If stock differs by variation, ask how the proposed setup will represent and manage it, and whether any connections to existing stock systems are included or treated as separate work.
Review the checkout as a customer would use it. Confirm whether guests can buy without creating an account, what information customers must provide, and whether the quote includes the checkout settings and testing needed for your preferred buying process. Ask what happens if a customer abandons or changes an order, and whether any requested checkout adjustments are standard configuration or custom development. Avoid assuming that a feature is included just because the platform may support it; check that the quoted work covers setting it up and verifying it.
List the payment methods you actually intend to accept. Ask which payment provider or providers the proposal assumes, who will create or connect the merchant account, and whether provider setup, test transactions and troubleshooting are included. Payment providers may charge transaction or other fees separately from the website project, so ask for these to be identified as ongoing costs rather than bundled into a build estimate. Do not share account passwords in a quote request; clarify the secure access or authorisation process with the provider.
For shipping, specify where you deliver, whether you offer flat rates, free shipping thresholds, local pickup or different rates by location, and how bulky or restricted items are handled. Ask whether the quoted setup uses manually configured rules or depends on an external service, and whether that service has its own subscription or requirements. For tax, clarify which regions you sell to and who is responsible for supplying the correct rates and settings. The provider can configure agreed rules, but you should confirm tax obligations with an appropriately qualified adviser rather than treating website setup as tax advice.
Accounts and promotions also need a practical test. Decide whether customers need saved details, order histories or account access, or whether guest checkout is sufficient. Identify the offers you plan to run, such as discount codes, sale prices or free-shipping thresholds, and ask which are included. If you do not expect to use a promotion type, do not pay for it merely because it appears on a feature list.
Request a concise feature schedule with each item marked included, optional, excluded or dependent on another product or service. Compare the same requirements across all quotes, and ask for the price and scope to be updated when a feature is essential but missing. This makes trade-offs visible: you can prioritise what customers need to buy successfully now, while leaving non-essential enhancements for a later phase. Check that the proposal also allows time to test the agreed customer journey before launch.
Allow for products and migration
Confirm what product and store data work is included
A quote that says “product upload” can cover very different amounts of work. Before comparing prices, estimate the size and condition of the catalogue that needs to be added or moved. Ask providers to state the number of products and variants included, along with any limits on categories, product images, attributes, downloadable files or other product details relevant to your store. A product with several sizes or colours may require more setup than a single product, so clarify how variants are counted.
Prepare a representative sample of your catalogue and share it with each provider where possible. Include straightforward products and the less typical ones, such as products with multiple options, bundles or different pricing. Ask whether information will be imported from a spreadsheet or existing store, entered manually, or handled using a combination of methods. Confirm who will supply the product names, descriptions, prices, SKUs, stock levels, images and category structure, and what format or level of completeness is expected.
Separate preparation, migration and checking
Moving data is not necessarily the same as cleaning it up. Ask whether the quoted work includes reviewing inconsistent formats, correcting duplicate or incomplete records, resizing or renaming image files, and organising categories or attributes. If these tasks are excluded, find out what condition your data must be in before work begins and who will prepare it. You may be able to do some preparation yourself, but agree on a template and requirements first to avoid rework.
If you are moving from an existing ecommerce platform, list the records that matter beyond products. These might include customer accounts, order history, discount codes, reviews or other store data. Ask which records can be moved, which will need another approach, and whether any information will be left behind. Do not assume that a quote covers every record just because it includes “migration”. Confirm who provides access to the old store and who is responsible for handling and checking exported data, particularly customer information.
Ask how the provider will verify the result before launch. Useful checks may include comparing product and variant counts with the source, reviewing a sample of records, and checking prices, images, categories and stock information. Agree who will identify errors, make corrections and approve the migrated catalogue. For existing product pages, ask how URL changes and any redirects will be considered, so that search engine visibility is not overlooked during the move.
Request a written allowance for the expected catalogue size and a rate or approval process for additional work if the estimate is exceeded or the source data is not ready. For example, a quote might include importing a stated number of products from a supplied spreadsheet but exclude rewriting descriptions or resolving inconsistent stock records. Making those boundaries explicit helps you compare the real workload in each proposal, not just its headline project fee.
Separate ongoing costs
Separate the build fee from the cost of running the store
An ecommerce quote can look affordable upfront but leave important operating costs unclear. Ask each provider to list one-off project charges separately from recurring costs, including how often each charge is billed, when it starts and whether it is optional or needed for the store to operate. Check whether amounts are GST-inclusive or GST-exclusive, and note which charges are paid to the provider and which go to another supplier.
Start with hosting and platform costs. A self-hosted store may have separate hosting, domain renewal and software or plugin subscriptions; a hosted ecommerce platform may charge a regular platform plan instead. Ask what the quoted arrangement covers, such as backups or routine technical support, and what is billed separately. Confirm who will hold the hosting, domain and platform accounts, and whether you can access them directly. If a service is bundled, ask what happens to the store and its data if you later move to another provider.
Request an itemised list of paid plugins, extensions, themes or other software licences the store will rely on. For each, clarify the renewal interval, current licence holder, renewal responsibility and what functionality might be affected if the licence lapses. Not every store needs paid add-ons, so ask the provider to distinguish essential components from optional recommendations. Also check for domain, security certificate or backup renewal charges if these are not included in another service; do not assume they are free or separately chargeable without checking the quote.
Maintenance should be described as a service, not just a line called “support”. Ask what work is included, how often it is carried out and how requests or urgent issues are handled. Routine updates, monitoring or backups may be included in a plan, while new features, content changes, troubleshooting caused by third-party services or work outside agreed hours may be charged separately. Find out whether maintenance is a required ongoing arrangement or can be managed by you or another provider, and whether there are minimum terms or notice periods.
Payment transaction charges are usually separate from the website build and may be charged by the payment provider. Ask which payment methods are assumed and check the provider’s current fee schedule directly. Depending on the provider and transaction, charges may vary by payment method or include other items, such as fees for refunds or currency conversion. Keep these variable charges distinct from fixed monthly subscriptions: their total will depend on your transactions, so avoid treating them as a set website cost.
To make the comparison useful, create a simple cost schedule with columns for the expense, supplier, billing frequency, amount or calculation method, and whether it is included in the quote. Record unknowns as questions rather than assuming they are covered. Ask providers to identify any costs that rise with product volume, storage, orders or usage, and request the basis for those charges. Compare expected costs over the same period, such as the first year, while keeping one-off setup fees separate from renewals and transaction-based expenses.
Finally, check what happens after launch: who sends renewal reminders, who can authorise charges, and whether you can cancel or transfer each service without losing access to essential accounts or records. A clear breakdown will not predict every future expense, but it lets you compare the ongoing commitment as carefully as the initial build fee.
Test quotes side by side
Turn every quote into the same set of questions
A quote is only easy to compare with another when both providers are responding to the same requirements. Send each provider the same written brief, including the store features you need, product numbers and any existing data to move. Ask them to answer against that brief in writing, rather than relying on different assumptions discussed in separate meetings. If a requirement is unclear, ask for it to be confirmed before comparing totals. A lower price may reflect a smaller scope, not a more efficient way to deliver the same store.
Ask each provider to list what is excluded, not just what is included. For example, clarify whether the price covers content or product entry, copywriting, photography, paid plugins, domain changes, staff training and the setup of payment or shipping services. Check assumptions such as who supplies product descriptions, images and account credentials, and whether those materials must be ready in a particular format. Ask about dependencies too: work may rely on you supplying content, approving designs, obtaining third-party account access or making decisions by agreed dates. Find out how delays or missing materials affect the schedule and any fees.
Have providers explain how they handle work that falls outside the agreed scope. Ask what counts as a change request, how you will be told its cost and timing, and whether approval is required before extra work starts. Clarify how many design or review rounds are included, how feedback is submitted, and whether corrections to an agreed specification are treated differently from new requests. Request an itemised estimate or written process for additional work; avoid relying on a vague statement that changes will be charged as needed.
Compare the testing and launch arrangements in practical terms. Ask what will be checked before launch, such as product and checkout flows, payment setup, shipping rules, mobile layouts and key pages, and who is responsible for providing test details or approving the results. Confirm whether the provider will assist with launch-day tasks, domain or DNS changes, and any agreed checks after the store goes live. Ask what support is included after handover, for how long, and how you can request help. Do not assume that “launch included” means ongoing maintenance or support is included.
Confirm who will own and control the finished store. Ask whose name will hold the domain, hosting and third-party service accounts, and whether you will receive administrator access, the finished site files and relevant documentation. Clarify any licence or subscription costs for themes and plugins, and whether they continue after the project ends. Make sure the proposal describes what happens if you later move to another provider, including any limits on access or transfer.
Hypothetical example: One quote includes product entry for a set catalogue size while another assumes you will upload products yourself. Compare the workload as well as the price: ask how many products and variants are covered, what information you must supply, and whether the provider will check the entries. A clear answer lets you account for your own time or ask for a revised, like-for-like quote.
Before choosing, put each provider’s answers beside the relevant line in the shared brief. Record unresolved questions and request written clarification or a revised scope. This makes differences visible, helps you plan the work you will need to do, and reduces the risk of comparing a complete proposal with one that leaves important tasks or costs undefined.
Conclusion: choose with clarity
Before choosing, compare the proposals against the requirements your store needs now, rather than selecting on the initial price alone. Check that the quoted work is clearly itemised, note any assumptions or exclusions that could affect delivery, and confirm what support is available after launch. Ask the provider to clarify anything you cannot compare, such as who is responsible for product information, what happens if requirements change, or which recurring costs are not included in the build fee.
Then consider the likely next steps for your business. You may need a larger catalogue, new delivery options or additional store functionality later, but avoid paying now for features without a clear purpose. Ask how future changes would be scoped and charged, and what access, documentation and account ownership you will receive. These details help you understand both the immediate commitment and the practicalities of managing the store over time.
Choose the proposal that offers the clearest fit between scope, ongoing costs and support—not simply the lowest or most elaborate quote. If important details remain unclear, request a written revision before you agree. A fair comparison gives you a sound basis for deciding what to buy now, what can wait and what responsibilities your team will take on.
Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.
