A Caribbean market that fits in a message
Bilingual online store for a Caribbean food market in Antioch, Tennessee: 84 products with their own pages, sold by unit or by case, and a checkout that ends in WhatsApp rather than a payment gateway.
- Client
- LIAMDA
- Business type
- Caribbean food market
- Service area
- Web & technology
- Location
- Antioch, Tennessee
- Year
- 2026
Services delivered
- Bilingual Web Design
- Custom Development
- Product Catalog
- Catalog Translation
- Policy Copywriting
- Accessibility
- Hosting & Deployment
The challenge
The business was already selling, and it was selling over WhatsApp. A photo of a handwritten list would come in, the back-and-forth would start —do you have this? what does the case cost? can you bring it Thursday?— and the order ended up written down by hand on the other end. The catalog existed, but as an export of 84 products across thirty categories that couldn't be shown to anyone. And there was a detail no generic store handles well: the two audiences buy differently. A household takes one unit; a corner store takes the case. Same product, two ways to buy it, and a price that has to be confirmed against the supplier's actual packaging. On top of that, half the customers read in English and half in Spanish, and part of the range —meats, frozen goods, dairy— leaves no room for improvisation on delivery.
What we did
We started from one decision that shaped everything else: no payment gateway. The business already closed over WhatsApp, and putting online payment in front would have added a step nobody asked for and a fee nobody wanted. So the checkout doesn't charge: it collects the details, composes the order —customer, delivery, lines with SKU, quantity and estimated total— and opens WhatsApp or email with all of it written out. The customer just hits send; what arrives on the other end is a readable order instead of a photo. The catalog is generated from the export itself with a single command, so updating prices means replacing a file and publishing again, not editing product pages one by one. All 84 products were translated into English indexed by SKU, and search looks at both languages at once: someone typing “pollo” and someone typing “chicken” find the same thing. Every product carries its purchase format —unit or case— with the note that case pricing is confirmed when the order is processed. And the four policies were written for what is actually sold: different claim windows for frozen goods and for pantry items, cold chain, and what cannot be returned for health reasons.
The result
The catalog can be shown. A link replaces the handwritten list, and the order arrives with SKUs, quantities and address —exactly what was needed to prepare it without asking again. The store works in both languages on the same product URL, so sharing a link keeps working even if whoever receives it reads in the other language. And the site is ready for the day online payment is needed: total calculation and order composition are kept apart from the interface, so adding a gateway is plugging it in, not rebuilding the flow.
The website, screen by screen
The same website, on mobile
Ready to start?
Tell us your idea and we'll show you how to make it a real company.
Let's talk about your project