Other industries — non-standard eCommerce projects

Your industry does not fit the standard categories, and your catalogue proves it

Configurable products, made-to-measure items, spare parts and compatibility, rental, subscriptions, appointment-based services, transport constraints: when the sales model is not 'add to cart', the project is built on requirements, not on a theme.

  • Requirements before the platform: technology is chosen afterwards
  • Non-standard sales models handled in the cart, not in notes
  • Integrations with the systems you already use, without redoing what exists
Let's talk about your project

We reply with a first read of your case, not a price list.

Tell us about your project

What you sell, how the product is configured and which systems you use today: we start from here.

We will get back to you to understand context, priorities and the best way to intervene.

PrestaShop Expert ★★★Sylius Professional Solution PartnerSylius Solution PartnerSince 2011100+ projectsBased in Catania, Sicily

Do you recognise yourself in any of these situations?

These are the situations of companies with a product or a process that standard templates do not cover.

  • Your product is configured: measurements, materials, finishes and options that exclude each other, and today the customer emails you instead of ordering because the cart cannot handle it.
  • You sell spare parts or components where compatibility with a model or machine matters, and without a selection guide you receive wrong orders that turn into returns.
  • The price depends on variables (quantity, measurement per square metre, finish, delivery distance) and has to be calculated, not read from a fixed price list.
  • You have quotes, site visits, appointments or subscriptions in the sales process, and today the site just shows a catalogue that leads nowhere.

What you get from a project built on requirements

Your sales model fits inside

  • Configurators with rules, dependencies and invalid combinations.
  • Quotes, appointments, rental and subscriptions handled in the flow.
  • Price calculated on variables, not just read from a price list.

A complex catalogue made navigable

  • Normalised technical attributes and filters that really help.
  • Search by code, reference and compatibility.
  • Data structure designed for feeds and integrations too.

Development and marketing in the same team

  • The people who build the site are the ones who then work on acquisition.
  • Less passing the buck between suppliers when something does not work.
  • Actions decided on data, not on the skills available.

What we look at when the sector is not specialised

The sector matters, but it is not the only variable: two companies in the same field can have completely different projects. These are the dimensions we analyse before proposing any solution.

How the product is composed

A finished product with a fixed code, an item with variants, a configurable product with compatibility rules or a made-to-measure item require different architectures. For configurators you need, before development, the list of options, the dependencies between choices, the forbidden combinations and how the configuration reaches production.

How the price is formed

Fixed price, tiered, per metre or by weight, calculated on measurements entered by the customer, dependent on finishes or delivery distance. When the price is the result of a formula, the formula has to be formalised and validated: it is the part of the project where mistakes cost the most.

What the unit of the order is

Single purchase, recurring reorder, subscription with renewals, rental with period and deposit, booking with calendar availability, service with appointment. Each of these models changes cart, payment, post-order handling and communications: they are not features to add at the end.

Where the data lives

Customer records, stock, price lists and orders often originate in an ERP or a PIM that remains the authoritative source. You need to decide which data to sync, in which direction, how often and what happens when the sync fails. The quality of existing data is the variable that moves project timelines the most.

What constraints delivery has

Bulky or heavy goods, pallet transport, delivery to the floor, assembly, dangerous or temperature-controlled products, areas not served, lead times tied to production. Each constraint becomes a rule in the checkout: if it does not fit, it becomes a phone call after every order.

Who will run the site every day

A sustainable project is one your team can run. If nobody in the company can upload products or update content, the right technical solution is different from the one for a company with a dedicated person. It is a question we always ask before choosing the platform.

What the project can include

The scope comes from your requirements: these are the components that recur in non-standard projects.

Analysis and requirements

  • Mapping of the current sales process, informal channels included
  • Formalisation of product, price and configuration rules
  • Assessment of the quality of existing data in the ERP or files
  • Reasoned choice of platform after the requirements, not before

Catalogue and custom development

  • Data model with normalised technical attributes
  • Product configurators with dependencies and invalid combinations
  • Search by code, reference and compatibility
  • Price calculation on formulas, measurements, quantities or finishes

Non-standard order flows

  • Quote request and conversion into an order
  • Subscriptions, recurring reorders, rental and bookings
  • Appointments and site visits integrated into the journey
  • Shipping rules for bulky, heavy or restricted goods

Integrations, marketing and continuity

  • Integration with ERP, management systems, PIM and external systems
  • Reliable eCommerce tracking and measurement of enquiries
  • SEO and campaigns built on your market's language
  • Ongoing support and further development after launch

Are we a good fit?

It is a good fit if

  • Your product or sales process does not fit standard patterns
  • You have a technical or configurable catalogue that is hard to represent online
  • You use management systems that must remain the source of data
  • You are looking for a supplier that starts from requirements, not from a ready-made theme

It probably isn't for you if

  • You need a quick, cheap showcase site without particular logic
  • Product and price rules cannot be formalised and there is nobody who can decide them
  • You want to start straight away without a requirements analysis phase
  • Your only selection criterion is the lowest quote

Frequently asked questions about non-standard eCommerce projects

Yes, on one condition: that there is time to understand how your market works before developing. The expertise we bring is technical and methodological (complex catalogues, integrations, conversion, acquisition), while knowledge of your sector comes from you. The analysis phase exists precisely to bring the two together, and it is why we do not offer pre-packaged solutions.

Almost always yes, but the hard work is not technical. You need to formalise the options, the dependencies between choices, the invalid combinations, the effect of each option on price and lead time, and how the configuration reaches production. If these rules exist only in the experience of the people who prepare quotes, the first part of the project is writing them down.

Yes, but these are models that change the structure of the project, not features to add at the end. Renewals, recurring payments, suspensions, rental periods, deposits, calendar availability and handling of returns have to be defined first, because they determine the behaviour of the cart, payment and customer area.

The one the requirements point to. We work mainly on PrestaShop (we are a certified Expert ★★★ agency) and on Shopify, and we take on projects with more particular needs when custom logic is required. Choosing the platform before understanding the sales model is the most common way to end up forcing a system to do what it cannot do.

It depends on the complexity of the rules and the state of the data, not on the number of pages of the site. On projects with configurators or ERP integrations it is the phase that deserves the most time, because it is where costly mistakes are avoided. At the end you receive a document with requirements, scope, phases and estimate: only then do you decide whether to go ahead.

Not necessarily. It is often better to work on the existing one, fixing data, integrations and conversion. A rewrite makes sense when the current structure prevents you from doing what you need or when maintenance costs exceed rebuild costs. We say so after looking at the project, not before: if your current site can hold up, we will not propose rebuilding it.

Does your project not fit standard patterns?

Tell us what you sell and how the process works today: the first thing we do is understand the requirements, then we tell you whether and how it makes sense to proceed.

No commitment: first we work out whether the project makes sense.

Tell us about your project

What you sell, how the product is configured, which systems you use and what you cannot do today: this is enough for a first assessment.

We will get back to you to understand context, priorities and the best way to intervene.