Products that are configured,
not picked off a shelf.

INNOMEGA IMX Commerce Platform drives our most complex client installations. A large e-commerce suite or ERP module can be forced into this shape, but it costs weeks of expensive staff time and still fits badly. IMX starts where your sales process already is.

Built for the way industrial companies sell.

Fire services, public agencies and industrial buyers rarely put something in a basket and pay by card. They need a specification that is right, a written quotation with a number and a validity date, and a purchase order that follows it. IMX is built around that sequence.

Each client gets an installation of its own: its own application, its own database, its own domain. No client shares any of it with another. Every installation runs the same code; only configuration and content differ.

We do not do consumer retail, marketplaces, card payment or self-service sign-up.

You buy the parts you sell with.

Catalogue, editorial content, configuration, quotations and customer organisations — in one installation.

Core is always included. Everything else is added when there is a reason to, so nobody pays for a quotation engine they do not use.

IMX Core running through the middle, with the Content, Shop, Accounts, Configure and Quote modules plugged into it and a slot left open Content Shop Accounts IMX Core Configure Quote +

IMX Core

Core decides who may do what, puts every tool in one administration, and reports how the business is going.

  • Permissions per person and per field, enforced on the server
  • Every tool in one administration, with a manual filtered to your rights
  • Revenue, orders and quotation conversion, each against the same period last year
  • Cookie-free visitor analytics: cities, devices, referrers, search terms
  • Transactional e-mail with delivery logs, translations, scheduled work, change logs

IMX Content

Your own people publish into fields. No HTML to learn, no layout to break.

  • Record types with fixed fields, defined to give structure, extensible by our clients
  • Examples: delivered vehicles — customer, chassis, type, gross weight, images; or a register of installed machines, where service teams see exact status and what the service level requires next
  • Editors get a fixed set of blocks, so pages stay consistent and work on every screen
  • The address on a record becomes a point on a map
  • Articles and galleries through the same image pipeline
  • Every change logged; records retired, never deleted

IMX Shop

The catalogue, and everything between finding an article and handing an order to your ERP.

  • Categories and articles maintained by your own staff
  • Search runs across every language at once, and every search term is reported back to you
  • Surcharge options and length- or weight-dependent prices
  • Shipping by weight, zone and carrier; delivery times set per article or article group
  • Ordering on account, status chain, ERP hand-off and CSV export

Includes IMX Accounts.

IMX Accounts

The customer is the organisation, not whoever happened to be at the keyboard.

  • Colleagues share orders, quotations and lists
  • Named delivery addresses: head office, workshop, project job site
  • Every article ever bought, with spare parts filtered to it
  • Invitations, roles, and a full change log

Included with IMX Shop.

IMX Configure

Your engineering rules, applied the same way every time, by anyone.

  • Sizing from the load and runtime values a customer already has
  • Technical filters that rule out what cannot work
  • Three solution tiers per result, with the trade-off stated
  • Total cost of ownership
  • Options and dimension pricing on ordinary catalogue articles

Includes IMX Quote.

More on configurators →

IMX Quote

Your customer’s purchasing department can process the quotation without ringing you back.

  • Number, validity date, PDF and an online view
  • States: open, ordered, ordered offline, discarded with a reason
  • Expiry reminders and a morning digest for sales
  • The requesting company is matched from its e-mail domain

From the first enquiry to the quarter-end reporting.

01

A configuration becomes a quotation

What Configure produces is a solution, and a solution has to become a document somebody can sign. Configure is therefore never sold without Quote.

02

A quotation becomes an order

Only while it is still valid. Prices are recalculated from your catalogue at conversion; the browser cannot set them.

03

An order belongs to an organisation

Colleagues see it, the delivery address comes from the organisation’s own list, and the purchase-order reference travels to your ERP.

04

Everything reports into one place

Orders, quotations, searches and enquiries all report into Core. Each number is shown against an equally long preceding period, so a running month is never compared with a finished one.

Content runs alongside that chain, on the same permissions, the same image pipeline and the same change log. The people who publish your handover reports are the people you already gave accounts to.

The same platform, assembled differently.

HENSEL Fahrzeugbau

Core, Shop, Accounts and Quote, with option and dimension pricing from Configure.

Makker AS

Core, Configure and Quote. The configurators size uninterruptible power supplies and generators from the customer’s own load and runtime values, and produce a quotation with the manufacturer’s documents attached.

Multiple complex configurators in production, including UPS systems up to 2,400 kW and diesel generators, currently in four languages.

Operated like infrastructure. Because your business depends on it.

Your data, in the EU

Servers and managed database in Frankfurt. One database per client. Commercial data is kept out of the content system, with a single service writing to it.

Backups and monitoring

Nightly database backups, container and memory monitoring with alerts, and a weekly check that the redirects from your old domain still resolve.

Updates stay ordinary

Your system is a layer on top of an unmodified open-source content core. Security releases apply as ordinary updates.

Access is per person

No shared logins. Two-factor authentication for staff, permission levels you define, and read-only fields where a level lacks the right, prices included.

Everything leaves a trace

Article edits, organisation changes, address changes, sign-ins: logged with person, time, and the value before and after. Every log has a retention period, set before the log is switched on.

Two environments

A development installation beside production, so a change is seen against real data before anyone else sees it. The platform carries a version, shown inside your own administration.

The CAPEX depends on the complexity of the build; the OPEX on the monthly platform cost and the service level.

Get a price for your setup 

The configurator price list shows what that looks like in practice, service levels and the high-availability option included.

What to ask before you commit.

Can we start with one module?

Yes. Core plus one is a normal starting point, and both installations in production grew that way. The only fixed rule is that Configure is not sold without Quote — a configuration that cannot become a quotation helps nobody.

Who owns the data?

You do, and it sits in a database that is yours alone. Orders export as CSV over any date range and as a paste-ready block in your ERP’s format; the catalogue exports too. Nothing is held hostage by design.

What if we want to move away later?

Your data leaves with you; that is the answer above. The application code is a different matter: it is our copyright, licensed for your installation. If the system has become business-critical and you want the code itself, we will discuss it, licensed to your company and not for resale, priced against several years of what running and supporting it would otherwise cost. The content system underneath is open source either way.

Do we need a second system for our website?

No. Editorial content runs on the same platform, through IMX Content, on your editorial installation. Website and shop can run as two installations of the same platform, neither able to reach into the other’s data.

How large can a catalogue get?

The database underneath handles tens of thousands of articles without flinching. What governs the sizing is concurrent traffic per application server, per installation.

Would this fit the way you sell?

In a no-obligation 30-minute intro call (in English, German or Swedish, by video or phone) you describe how quotations and orders reach you today, and we say plainly which modules would earn their keep and which would not.