e-commerce in parma: costs, timelines and five mistakes i see
web · 2026-10-24 · 6 min
an e-commerce quote is not a number. it is a set of decisions wearing a number as a coat. when someone asks me "how much does an online shop cost in parma", the honest first answer is that the platform is the cheapest part and the catalogue is the expensive one.
i build websites in parma, italia. these are the ranges i use when planning a small shop, the three roads i compare, and the mistakes i see often enough to write them down.
the three roads, with honest ranges
shopify. subscription around 30-40 euro a month on the plan that actually sells, plus a theme, plus the apps that do the things the base product does not. a small catalogue can be live in four to six weeks. the real cost is the subscription forever and the apps that creep in: reviews, email, bundles, translations. the ceiling is high and the floor is comfortable.
woocommerce. hosting 10-40 euro a month, a theme, a handful of plugins, and someone who updates them. cheaper on paper, more expensive in attention. six to ten weeks for a small catalogue, more if the shop has variants, shipping rules or an erp to talk to. the plugin stack is the product, and the plugin stack is also the maintenance.
custom, usually react or next.js on top of a commerce api. typically 8,000-25,000 euro for a small shop with a real design and a checkout that is not a template, before content and photography. three to six months. it wins when the shop is the product, when the catalogue is unusual, when the buying flow is the differentiator, or when the site has to do something no plugin does without three more plugins.
these are planning ranges, not market averages. a quote in parma can be lower and a quote in milan can be double, and neither tells you which one is right for your shop. what matters is what the range includes.
what the range should include
- catalogue structure and a way to add products without calling the developer
- product photography direction, even if you shoot it yourself
- shipping, taxes, returns and the pages that explain them
- payments, including the one local customers actually use
- checkout tested on a real phone, on a slow connection
- analytics and one conversion event you can read
- a maintenance plan, because a shop is never finished
if a quote does not name these, the number is not comparable to another number that does.
five mistakes i see often
1. choosing the platform before the catalogue. the platform decision is a consequence of how many products, how many variants, how often they change and who updates them. deciding shopify first and fitting the catalogue after is how a shop ends up with 400 variants nobody can edit.
2. a catalogue with bad photos. the product page is the shop. if the photo is a phone snapshot on a kitchen table, the checkout does not matter. this is the cheapest fix and the one most often postponed.
3. shipping and returns explained at the end. the cost of delivery and the right to return are part of the price. hiding them until checkout is how carts are abandoned and how support tickets are born. put the numbers on the product page, in plain language.
4. no measurement. a shop without analytics is a shop with no idea which page sells and which page scares people away. one counter, one purchase event, one look per month. that is the minimum, and it is not optional.
5. treating launch as the end. stock changes, prices change, a payment provider changes its rules, a plugin breaks. a shop needs an owner after launch, and that owner is either you with a plan or a developer with a contract.
when custom actually wins
custom is not "better". it is a different trade. it wins when the buying flow is the product: a configurator, a subscription with unusual rules, a b2b portal with negotiated prices, a catalogue that comes from a system you already run. it loses when the shop is a normal shop, because a normal shop is a solved problem and paying to re-solve it is a hobby.
the honest test: can you describe, in one sentence, what the custom build does that shopify or woocommerce cannot do without three plugins and a compromise? if the sentence is vague, the custom build is a preference, not a requirement.
what i would do first
before comparing platforms, write the catalogue: how many products, how many variants, how often they change, who writes the descriptions, who takes the photos. then write the order: how it is paid, how it ships, what happens when it comes back. those two documents decide the platform more than any comparison table. they also make every quote comparable, which is the only way to buy this well.
for the checklist version of this, see how to create an ecommerce website for a shop. for the pricing side of a normal site, see how much a website costs. for the service in parma, see realizzazione siti web a parma.
faq
how much does an e-commerce cost in italy?
for a small shop, the honest planning range is 2,000-6,000 euro on shopify or woocommerce including setup, theme, a reasonable plugin stack and the pages around the catalogue, and 8,000-25,000 euro for a custom build. photography, copy and product data are usually extra, and they are usually the bigger number.
how long does it take?
four to six weeks on shopify for a small catalogue, six to ten on woocommerce, three to six months custom. the variable is not the platform. it is how ready the catalogue, the photos and the shipping rules are when the project starts.
shopify or woocommerce?
shopify if you want the least maintenance and you accept the subscription and the app stack. woocommerce if you already run wordpress, want control and have someone who will maintain it. neither is wrong; the wrong choice is picking one before you know how the catalogue behaves.
when is custom worth it?
when the buying flow itself is the differentiator: a configurator, unusual subscription rules, a b2b portal, a catalogue tied to an existing system. for a normal shop with normal products, a normal platform is the better engineering decision.