Umbaji in Kenya
A market, not a shipping destination. Kenyan materials, Kenyan lead times, Kenyan delivery expectations, and pricing that reads as native rather than converted.
Why Kenya, and why now
Kenya does not need 3D printing explained to it. Nairobi already runs a dense layer of fabricators, machine shops and design studios, and the constraint has never been appetite: it is that the machines, the materials and the people who can run them arrive separately, from different importers, on different timelines, with nobody accountable for the gap between them.
That gap is the whole reason this market is built as a market rather than as a shipping destination. A printer bought abroad lands with a 12 week lead time, a warranty that means nothing locally, and a spool of filament that has crossed the equator twice. When it stops working, the person who sold it is in another timezone and the person who has to fix it has never seen one.
Umbaji sells the machine, commissions it on site, trains the operator, and keeps supplying the consumables. Prices are quoted in shillings because a quote that arrives in dollars is a quote somebody has to do arithmetic on before they can take it to a finance committee. Delivery is modelled on Nairobi and upcountry distances because those are the distances that exist.
Delivery map
Nairobi leads; the corridors are the delivery tiers, drawn.
12 wk
typical import lead time this replaces
Umbaji estimate, based on customer-reported waits for directly imported machines
Same day
Nairobi delivery, ordered before noon
Umbaji delivery tier, from the market record
4 rails
ways to pay, led by M-Pesa STK Push
Umbaji payment configuration, Paystack gateway
Held and displayed in KES
Country detection on arrival with a manual override that persists. A quote raised in KES stays in KES through checkout, receipt and refund: currency drift between quote and invoice is a common and entirely avoidable source of disputes.
KES
Everything is priced, quoted and invoiced in KES.
Paystack
Settlement runs through Paystack, to a local account.
4
Led by M-Pesa, the way people here actually pay.
4
Modelled on this market鈥檚 real distances, not converted from another鈥檚.
How customers pay
4 rails through Paystack. The primary one leads because it is what most people in this market reach for first.
M-Pesa
STK Push: the prompt is raised on the customer鈥檚 phone and confirmed in place, rather than sending them away to type a paybill number and reference by hand
Airtel Money
The same flow, no separate page
Cards
Local and international Visa and Mastercard, settling to a Kenyan account
Bank transfer
For institutional orders too large to sit comfortably on a card
Tax and compliance
Fields a Kenyan business actually needs
KRA PIN
Captured on business orders so invoices are usable for input tax
Organisation name
Held on the order record alongside the PIN
eTIMS-ready numbering
The field exists and is populated. Formal integration later is a connection, not a migration
Delivery and lead times
4 tiers, on this market鈥檚 distances
Nairobi same-day
Courier within the city, ordered before noon
Nairobi next-day
Standard metro delivery
Upcountry
Courier to major towns, 2 to 4 days
Workshop pickup
By arrangement
Kenyan turnaround tiers are modelled separately from the US ones, because they are genuinely different numbers.
Built to add a market, not rebuilt for one
Currency, payment rail, tax fields and delivery tiers are properties of a market record. Adding a second African market is populating that record and wiring a rail.
馃實
Next market
/markets/[country]