Can we run more than one product together?

Yes, and it is a common arrangement — forecourt automation with a convenience-store POS, or point of sale with physical security across several sites. They share user management and reporting, so it is one login and one set of numbers rather than two vendors to reconcile.

Which product should we start with?

Whichever runs the part of your business that hurts most today. Starting with the highest-friction operation gives you a result you can actually feel within weeks, and it tells you far more about whether we are the right vendor than a longer evaluation of everything at once would.

What if none of these fit?

Then it is a custom software conversation rather than a product one, and we have a page and a practice for that. Forcing an operation into the nearest available product is a decision that looks efficient at signing and costs you daily for years afterwards.

How much of this is actually deployed?

Pacific POS is running live transactions in real businesses. Six deployments across restaurants, retail, education, print, physical security, and custom development are written up in full as case studies. Products without one are shipped software that has not yet earned a published deployment story, and we mark that distinction rather than blurring it.

Products

Fifteen products, one platform

Purpose-built products that each run one part of a business well — on shared payments, reporting, hosting and access control.

Product lead walking through the Merilsoft application catalog on a wall display

The catalog

15 products, one platform underneath

Each runs one part of a business well. Together they share one login, one set of numbers and one support team.

Browse by shelf

15 products

Digital Sign Solution

Indoor, dual-side & POS signage, managed remotely

Learn more

How the catalog is organised

Four groups, and what each is for

Run your operations

Day-to-day systems for people, assets, and back office.

Serve your customers

Customer-facing platforms for what you sell and teach.

Proof

Shipped, deployed, written up

Engagements documented start to finish — the operation before, what we built, and what changed.

AI restaurant ordering system

A Family-Owned Restaurant

A family-owned restaurant: orders transformed, errors dramatically down

A family-owned restaurant replaced manual order-taking with Merilsoft's AI-driven restaurant ordering system — and changed how the whole restaurant runs.

Cut to a rare exception, not a nightly occurrence· Kitchen re-fires from mis-keyed ordersRead the case study

FAQ

The catalog, answered

Because the domain model is the part that has to be specific, and the infrastructure underneath it does not. Payments, reporting, access control, and hosting are built once and shared by everything; what gets built per product is the model of the work — a menu, a patient encounter, a tank and a shift. That is the split that makes a fifteen-product catalog viable rather than spread thin.

The catalog

How fifteen products stay this deep

Layered interface panels from a product design workspace

A catalog of fifteen products raises a fair question: how does one company build fifteen good ones? The honest answer is that we do not build fifteen from scratch. Every one of them is built on the same foundations — the same authentication, the same reporting layer, the same hosting and access control, the same payment rails where money moves.

What differs between them is the domain model: what an order is, what a record contains, what has to reconcile against what. That is the part worth building carefully per product, and it is the part a configurable general-purpose tool cannot reach. Everything underneath it is shared, which is why the catalog can be this wide without being this thin.

The practical consequence for you is that products compose. A fuel site runs forecourt automation and a convenience-store POS as one system with one login. A multi-location retailer runs point of sale and physical security together. You are not integrating two vendors; you are switching on a second module of the same platform.

Depth is not uniform across the catalog and we would rather say so than imply otherwise. Our point of sale has the deepest deployment history. Several products have a written-up case study attached. Others are real, shipped software without a public deployment story yet — those pages describe what the software does rather than inventing a customer to have used it.

Fifteen products, one platform