What defines the scope of an online store in Argentina: what to know before you start

As a Forward Deployed Engineer, one of the questions I get most often from SMBs and entrepreneurs is how an online store gets built and what makes it simpler or more complex. There's no single answer, which is why this article has no numbers: I share the factors that define the scope and effort of an ecommerce project in Argentina and how I evaluate them at the start.

The idea is that you can approach a conversation with a professional, whether me or someone else, knowing which questions are worth asking.

Platform-based store vs. custom-built store

There are two main paths when setting up an ecommerce, and choosing the right one from the start avoids rework.

Store with CMS/platform (WooCommerce, Tiendanube): this is the path I usually recommend to most SMBs that are starting out or consolidating their online sales. You start from an already-built foundation (WordPress + WooCommerce, or Tiendanube) and on top of that you configure catalog, payment methods, shipping, and visual design. Typical delivery times range from 3 to 5 weeks.

Custom-built store: here the system is built from scratch, without relying on a pre-built platform. It makes sense when you need particular business logic, complex integrations, or a product that doesn't fit the standard CMS mold. Typical timelines range from 5 to 8 weeks.

The difference in effort between the two paths has a concrete reason: on a platform, a large part of the heavy lifting (cart, stock management, payment gateways, admin panel) is already solved and tested. In a custom build, all of that has to be built, tested, and maintained.

Which factors define scope and effort

Within each path, there are specific variables that make a project more contained or more complex:

• Integrations. Connecting the store with an ERP, a billing system, a CRM, or an external stock management system adds development and testing work that isn't part of a basic installation.
• Electronic invoicing. If the store has to automatically issue A/B invoices or integrate with AFIP/ARCA and the accounting system, that's an extra layer of complexity, not a checkbox that ticks itself.
• Custom design. A configured theme personalized with the brand is one thing; a 100% custom design, with unique components and a user experience built from zero, is another. This can move the project from platform territory into custom development.
• Number of products and variants. This doesn't define development effort as much, but it does affect the initial loading and configuration time.

What keeps a project more contained: a clear catalog from the start, standard payment methods (like Mercado Pago), a design based on a well-chosen template, and no unusual integrations.

A typical case: WooCommerce + Mercado Pago for retail

A combo I put together frequently for retail SMBs is WooCommerce integrated with Mercado Pago. It's a robust solution, well known to Argentine buyers, with a proven checkout that avoids reinventing the payment gateway. For a retail business that needs to sell online without friction, this setup usually fits within the CMS store path, in 3 to 5 weeks.

Typical delivery times

To plan launches, campaigns, or stock:

• Platform-based store (CMS): 3 to 5 weeks.
• Custom-built store: 5 to 8 weeks.

These are the typical times for the complete process: scope definition, configuration or development, content loading, testing, and going live. A project with complex integrations or automatic invoicing can approach the upper end, regardless of which path is chosen.

How I evaluate a project before starting

When a small business reaches out, I start by understanding the business before the technology. I review what is sold and with which variants, how payment is collected, how orders ship, which systems already exist, and whether there are invoicing requirements. With that I place the project in one of the two paths and spot which factors from the list above weigh the most. If something is ambiguous, I'd rather say so and narrow the scope than overpromise.

How to choose without overcomplicating

If you're just starting out or your operation is relatively standard (product catalog, payment via Mercado Pago, traditional shipping), a platform-based store gives you speed and less complexity. If the business has particular processes, needs to integrate existing systems, or user experience is a key differentiator, that's where custom development starts to be justified.

The important thing is not to add complexity that isn't needed, nor to fall short with a platform that can't grow with the business.

What I took away

• The first factor is choosing between a platform and a custom build based on the business's real needs.
• Integrations and electronic invoicing are the factors that add the most complexity.
• Custom design can change the type of project, not just its size.
• A clear catalog and standard payment methods keep the scope contained.
• Defining the scope before starting avoids surprises during the project.

If you're thinking about an online store and want to talk through the scope, you can write to me on LinkedIn. And if it's useful, on my website I describe how I approach this kind of project: estebanburgos.com.ar/quote.