Define a product or service once. Your agents answer 'do you have it?' from it, quotes price from it, invoices bill from it, inventory counts it — all by reference. Change a price once and everything downstream is correct.
Catalog is the single source of truth for what you sell. CRM interests, invoices, inventory and the agents all reference items by ID — so they can never disagree.
An item lives in exactly one place. The CRM links to it, the invoice prices from it, inventory counts it, the agents quote it. Change the price in Catalog and every quote, bill and answer updates at once — there is no second copy in a spreadsheet to drift out of sync.
Every product and service has one record. The rest of the suite points at it by ID.
Update once; quotes, invoices and agent answers all reflect it immediately.
There's no duplicate copy to fall out of date. Consistency by construction.
Retire an item without breaking the invoices and history that reference it.
Organize the catalog the way your business thinks about it.
Specs, images and notes the agents can draw on to answer well.
Deliver semantic catalog queries across multiple languages locally using pgvector and E5 embeddings, with zero reliance on cloud LLM endpoints.
Softknack Catalog integrates a local transformer pipeline ('multilingual-e5-small') running directly inside the database node. Search queries in English, Tamil, Hindi, or Telugu resolve natively against embedding vectors using cosine similarity.
Not just SKUs: services with durations, resources and prerequisites — exactly what SK Calendar books against.
A haircut, a service visit, a consultation: each is a catalog item with a duration and the resources it needs. That's what makes it bookable in SK Calendar with correct availability — the catalog and the calendar speak the same language about what a 'service' actually is.
How long it takes is part of the item — so the calendar books realistic slots.
A service that needs a bay and a tech says so; availability respects it.
Catalog services flow straight into SK Calendar — no separate setup.
One catalog for both — the AC and its fitting service, modeled together.
A service that needs a prior step encodes it, so nothing's booked out of order.
Package services together — priced and booked as one.
Define branch-specific prices, local tax variables, currencies, and inventory limits for a single product without cluttering your global catalog.
Softknack Catalog supports nested price and stock overrides. Local variations inherit standard definitions from the global catalog page but define custom overrides scoped to specific branches or regions, avoiding duplicate stock definitions.
Catalog is deliberately not a storefront — it's a record you serve over the API, subscribe to via webhooks, and expose to agents over MCP with scoped permissions.
Most product systems lock your data inside their storefront. SK Catalog does the opposite: it's a clean system of record you read over REST, react to over webhooks, and expose to AI over MCP. Your own agents get the same scoped tools ours do — so you build on your catalog instead of being held by it.
Read and write the catalog programmatically — the foundation, not an afterthought.
item.updated, price.changed — your systems react the moment the catalog moves.
Expose the catalog to AI agents with scoped permissions — yours and ours alike.
Deliberately headless — feed any storefront, any agent, any channel from one record.
Fine-grained permissions on who and what can read or change.
Same auth, idempotency and conventions as every other SK product.
SK Catalog lives on the same customer record, the same events and the same rails as the rest of the suite.
Start free See the developer surface →