Built for manufacturers of heavy machinery, production lines, and long-life equipment. A catalog that gets you found - then a record of every machine in the field, part by part. On your infrastructure. Your domain. Your rules.
The buyer is rarely on your homepage. They are with a distributor, in another country, looking for a machine from a company they have never heard of. What they get today is a PDF, a one-language site, and an inbox that cannot say who earned the lead.
Native catalog is the shop window, not a shop. It runs on your domain, under your branding, in the language the buyer actually uses - 37 of them. They find the product, ask for a quote, and a person on a desk claims it.
Nobody searches for your company. They search for 60 litres a minute at 250 bar with a DN32 flange. They buy from whoever comes back with that.
Categories and free text cannot answer it. This catalog can: attributes are typed, defined once, then applied across a whole family. A filter is a real query against real values - not a text tag hoping for a match.
AttributeDefinition → AttributeSet → AttributeValue
Somebody is going to ask an assistant who makes a 400-tonne press with a heated bed. Most catalogs make it scrape three pages and guess. This one hands it the whole catalog.
A public catalog publishes more than a sitemap. We are talking Bulk JSON, schema.org, ItemList, llms.txt. Basically all the surfaces a person needs, and the surfaces a machine can actually read.
Flip the catalog private and every one of them returns 404. Being findable is a switch you hold - not a default you inherit.
You sold Model 400s. In the field they are no longer one product. One was commissioned in March 2022. Second one three years later. They have different parts in them and their maintenance will not need the same thing next month.
So each physical machine gets its own record: the name - “Line 2 press” - the serial plate, the day it went into service. Three presses on one floor means three different records. Not one card saying Model 400 × 3.
Scrap one and only that machine goes quiet. Sell it on and the record moves to the new owner. The others do not change.
Every unit keeps a history of what was fitted, where, and when. Keeping the source for everything after it - the clock, the warnings, the next request. Maintenance therefore never drifts out of sync.
When the customer sends a parts request and it is fulfilled, those parts are written back onto the machine. The record does not stop at “they asked.” It becomes “this is what is fitted in there now.”
How long a part lasts depends on where it sits. In the ram it may be six months. In the pump, eighteen. Same seal. Same press. Different job.
You set the component replacement interval on that machine, that part, that position, with the right amount - independently for each component when needed. That means your customers never order less than they need.
FLoCK™ does not store a due date for someone to go stale. It calculates it from the exact machine's start date and what the history says was last fitted there.
Your customer opens their machine and sees the parts it needs. One button sends you a request with the numbers you still sell - not the obsolete one, and not the same part three times.
They can take a line off. Press the button again and it does not come back. You receive a request you can fulfil, instead of a phone call asking which number to order.
Your staff are not all administrators. One person can work the inquiry desk. Another may publish the catalog. Another looks after customers and the machines in the field. Each sees only the languages, lines, and accounts they are responsible for.
Distributors get their own workspace: their links, the inquiries they earned, the customers in their book, and those customers' machines. Credit is stamped when the inquiry arrives and does not move when you forward the work.
A customer company gets its own login. They see their machines, their history, and what the Watcher says is due. They can invite their own colleagues - a second shift, a stores person - but always inside a ceiling you set. Lower the ceiling and it applies to people already in.
Not a general alert, but four separate reasons, closed separately. Clearing “there is a newer part number” does not also clear “this one component is due for service.”
| Reason | What happened | Who sees it |
|---|---|---|
Newer part number |
This part now has a replacement number. Request the new one, not the old one. | You and the customer |
No longer made |
It is out of production, and nothing has been named to replace it. It keeps asking until somebody does. | You and the customer |
Changes together/Dependency |
Another part on this machine in the same group changed, so this one may have to change with it. | You and the customer |
Service due |
The replacement date for this one machine has passed, or is close. | The customer |
Who runs your machines, and what is fitted in them, stays in your building. You install it on your own server, on your own domain, with your own database.
We only check that the licence is valid and that new features and updates are shipped to you to enhance your productivity. The catalog does not leave. The customer list does not leave.
How access worksWhether you are a startup or an established company, our plans give you the flexibility you need. Start simple and expand your capabilities when the time is right.