Loading
How it worksWhat you buyFor cafésFor suppliersApply as a caféApply as a supplier

For cafés

Stop running procurement
out of a phone.

You did not open a café to reconcile delivery notes. Here is what changes on the first Monday.

Monday morning

What changes, line by line.

Five things that take up your week, and what each one becomes.

Ordering
TodaySix chat threads, a rep who is on leave, and a price you agreed verbally in March.
Approving
TodayThe owner is copied on everything, or on nothing.
Receiving
TodayTwo crates short. Somebody writes it on the delivery note. The note is lost.
Paying
TodayForty invoices, forty transfers, and a reconciliation nobody enjoys.
Knowing
TodayYou find out packaging went up when the invoice arrives.

Your team

Who does what

Permissions are per person, per site, per category and per amount. A café with one site can leave every one of them alone.

  • 01
    OwnerSees everything. Sets the limits. Rarely has to use them.
  • 02
    ManagerOrders for their site. Approves up to the amount you set.
  • 03
    BaristaRequests what is running out. Cannot commit money.
  • 04
    FinanceSees invoices, statements and payments. Cannot change the catalogue.

What you get

Everything you buy, running on one record.

Open any card for what actually happens underneath.

One place to buy

Every supplier and every product you already use, in one catalogue you can search.

Suppliers load their own price lists. Silsilah maps different listings of the same product onto one record, so a 1kg bag from three roasters is comparable rather than three unrelated entries. Your contract prices sit underneath your own account, not in a public list.

One cart, every supplier

Fill one basket from four suppliers. You see one order and one total.

Underneath, Silsilah creates a separate order per supplier, each holding that supplier's own price, minimum order value, cut-off time and delivery promise. You never manage that split. It just has to be right, and it is recorded.

Approvals that fit your team

Set a limit. Under it the order goes. Over it, it waits for a person.

Limits can be per order, per day, per month, by branch, by category or by supplier. A requester cannot approve their own request. Above an amount you choose, two people must sign. A single café can ignore all of this. A group with twelve sites can turn it on without changing anything else.

Delivery you can see

Accepted, preparing, dispatched, on the way, at the door.

The supplier's own driver does the delivery. Silsilah provides the shared record, so nobody has to phone anybody to ask where an order is. Drivers work from a link on their phone, not an app they have to install.

What arrived, not what was ordered

Accept at the door, or record what was short, damaged or wrong.

Your team records the discrepancy by item and quantity with a photo, a time and a name attached. That becomes the goods received note, and the credit comes from it automatically. No arguing at month end from memory.

One bill, not forty

A single statement across every supplier, and one payment to settle it.

Each supplier invoice is matched against its order, the delivery and the quantities you actually accepted. Anything that does not match is flagged for a person rather than quietly forced into agreement.

One record

Order. Receive. Pay.

The same three things you already do, written down as they happen, on a record that does not break.

ORDER01

Ask, approve, send

Silsilah finds the products, compares the suppliers and drafts the order. Somebody with the authority approves it. Then it goes.

RECEIVE02

Confirm at the door

Accepted, preparing, dispatched, delivered. Your team accepts or reports a shortage with a photograph, and the credit note comes from that record.

PAY03

Settle once

One statement across every supplier. One payment. Every line matched back to its order, its delivery and its invoice.

  1. 01AcceptedTue 16:20
  2. 02PreparingWed 04:10
  3. 03DispatchedWed 05:35
  4. 04On the wayWed 05:41
  5. 05At the doorWed 06:04

Both sides read the same line. Nobody has to call to find out where an order is.

Coffee

Buy coffee by how it tastes, not by how it is described.

Most people buying coffee for a café are not cuppers, and should not have to be. Answer four questions and Silsilah narrows a hundred lots to the few worth tasting.

  • What are you brewing?Espresso, filter, Arabic, cold brew or decaf.
  • What should it taste like?Chocolatey, nutty, fruity, sweet, floral or balanced.
  • How bright?Low, medium or high acidity.
  • What is your budget and volume?Per kilogram, and how often you need it.
  • Request a sample
  • Roaster sends it
  • You taste it
  • Say what you thought
  • Order or agree supply
Too acidicToo darkToo fruityToo bitterGoodPerfect

Say it was too bitter and the next set of suggestions moves. The reasons are always shown, and anything a roaster has paid to promote is labelled as such and kept out of the recommendation.

If you do know your coffee

Origin, farm, process, varietal, altitude, score, harvest and roast profile are all there for the people who want them. They are just not the first thing anybody is asked.

Underneath

Simple on top. Strict where the money is.

A café with one site should never see any of this. A group with twenty needs all of it. Both get the same product.

Branches and budgets

One account, every site under it, each with its own limits and its own spend.

One history, kept

Every order, delivery, credit and payment stays. Corrections are new entries. Nothing is silently edited, by anyone.

Nothing forced to match

If an invoice disagrees with the delivery, it goes to a person. The system does not quietly make the numbers agree.

Suppliers paid on terms

Settlement follows accepted goods and the agreed terms, in one transfer with a statement behind it.

What the AI does, and what it never does

It does

It reads supplier price lists and catalogues so you do not have to. It understands a request written in ordinary words. It compares options, drafts the order, pulls the numbers off an invoice and checks them against what was delivered. It tells you why a cost moved.

It never

It never moves money. It never releases a payment, issues a refund, changes a limit or approves anything. It prepares work. A person with the authority decides. That is a rule in the architecture, not a setting.

The chain

means chain. This is the one we connect.

Thirteen steps run between needing something and the supplier being paid for it. Every one of them exists in your café today. Most of them are not written down anywhere.

Break any link and the rest becomes guesswork. That is the job.

Questions

The things people ask first.

We only have one café. Is this too much?
No. With one site you will never see a budget, an approval rule or a branch. You order, you receive, you pay once a month. The control exists for the groups that need it and stays out of the way for everybody else.
Do my suppliers have to be on it?
No. They can keep receiving orders the way they do now. The difference is that the order arrives complete and priced instead of as a message at midnight. Suppliers who do join get a portal, one statement and a settlement date they can plan around.
What does it cost a café?
Nothing to use. You pay for what you buy, at the price you agreed with the supplier.
Is my pricing visible to other cafés?
No. Contract prices belong to your account. Suppliers see their own customers. Nobody sees another café's terms.
Can it spend money on its own?
No, and that is deliberate. Nothing leaves your account without an approval from somebody who has the authority to give it. You set the limits and the system holds them.

Apply

Apply as a café

Six questions. It tells us whether we can be useful to you yet, and which suppliers we need live in your area first.

What do you buy?

We use this to contact you about launch. Nothing else, and no list sharing.