National Distribution CompanyFMCG distribution and wholesale
National Distribution Company sources, warehouses and distributes FMCG brands across Oman. We built the platform its trade buyers and brand principals use to browse the catalogue, read the network and warehousing story, and raise an enquiry. It is an FMCG distribution platform rather than a shop, so trade buyer portal development set the shape of every screen.
Build fingerprint
Where it runs, how we engaged, and what it was built on.
Technologies
What makes this problem genuinely hard - before any client name enters the page.
A principal manufactures. The distributor takes title to the stock, clears customs, holds it at the right temperature, breaks pallets into cases, runs a salesman past a few hundred outlets, executes the promotion the principal funded, extends credit to the trade, chases collection, and reports sell out data back. Its margin is the spread between landed cost and trade price, minus the cost of holding and moving.
There is no cart, and there should not be one. Price is contractual: it moves with the customer, the credit term, the volume band and whatever the principal funds this quarter. Publish a number and you hand every buyer a starting position. The job is discovery instead. A buyer confirms you carry the brand in the pack they stock, then starts a conversation. Filter, compare, enquire. The measure is qualified enquiries, not conversion rate.
Arabic is the official language, English is common in trade, so both are load bearing. The Arabic side is a layout problem before it is a translation one. Brand names stay in Latin script inside Arabic sentences, and those mixed runs reorder under the bidirectional algorithm unless interpolated text is isolated. Search also has to normalise alef and taa marbuta variants or Arabic queries return nothing.
The logo wall is the credential. A principal weighing an appointment reads it for channel conflict, checking whether a competitor already sits in the portfolio. A retailer reads it to work out how many brands one purchase order covers. Both arrive asking about a named brand, so brands need to be structured records carrying category, origin and pack range, not an image grid. Treat it as decoration and your most commercial page becomes unsearchable.
National Distribution Company sources, warehouses and distributes FMCG products across Oman. It faces two directions: up towards brand principals who need national coverage here, and down towards retailers, wholesalers and institutional buyers who order from it. One site serves both. A principal wants network reach, warehousing and category fit before opening a conversation. A trade buyer wants one answer quickly: do you carry this brand, in what pack. Both arrive on a brand name in search, and both leave through the same enquiry form.
Browsable by brand, category and pack, with enough detail for a trade buyer to identify the item they stock. No cart, no price, no account wall.
Each partnership is a record carrying category, origin and related products, on its own page. That is where a brand query should land.
Catalogue entries, brand records and media are edited by staff, not developers. A delisted SKU is an editorial action, not a release.
A distributor site is photograph heavy, and photographs are what make it slow. Media handling, metadata and page structure were part of the build, not a pass at the end.
Tradeoffs
Every choice closed off something else. Those costs are stated, not hidden.
Instead of: A B2B storefront with logged in customer price lists. Pricing is contractual per customer, and a login wall hides the catalogue from the brand searches that bring buyers in.
What we acceptedNo self serve reorder, so repeat orders still go through a salesperson and the site cannot attribute revenue.
Instead of: A hosted ecommerce platform. The requirement is listing, filtering and enquiry, and a commerce platform charges you in complexity for a checkout nobody uses.
What we acceptedAdding buyer ordering with account pricing later is a build, not a settings change.
Instead of: One partners page with a grid of logos. The brand name is the query, so it needs a URL, related products and metadata.
What we acceptedMore editorial work per brand at launch, and a half filled record reads worse than none, so the CMS needs required fields and an owner.
Reusable
The model we work from on distributor builds.
| Field or behaviour | Consumer ecommerce | Distributor trade catalogue |
|---|---|---|
| Price | Public, one per SKU | Contractual, by customer and volume band |
| Unit of sale | Each | Case, layer or pallet |
| Buyers search on | Product name | Brand, then category, then pack |
| Success metric | Conversion rate | Qualified enquiries by brand and buyer type |
| Who edits it | Merchandising | Brand and sales managers, so CMS is mandatory |
| Refresh cycle | Continuous, feed driven | Bursty, tied to listing wins and delistings |
The last row is the one teams underestimate.
Delivery
Capabilities delivered and the scope of the build - not results attributed to it.
Capabilities
Scope
Scope of the build, not results attributed to it.
Bring us the part you think is hardest.
Catalogue, brand records and media are edited by the client's team through the CMS. Nothing routine needs a developer.
Hosting and the domain sit with the client, so changing supplier is a commercial decision.
The platform is public, with no customer accounts or payment data, so the security surface stays small.
Reflection
Catalogue decay is the real long term risk and we underweighted it. FMCG listings change every quarter, and a public catalogue still showing a delisted brand costs credibility with principals and buyers at once. We would now put a last reviewed date on every brand and product record, and surface a stale queue in the CMS, rather than trusting editorial discipline. We would also instrument enquiry outcomes from day one, so reporting says which brands generate contact, not which pages generate traffic.
Trade pricing is not a published number. It moves with the customer, the credit term, the volume band and the promotional support the principal funds. A public figure hands every buyer a starting position. The catalogue confirms the brand and pack are carried, then hands off to a conversation.
Build work. A fully Arabic page mirrors cleanly, but distributor content mixes scripts, because brand names and pack codes stay in Latin. Those runs reorder under the bidirectional algorithm, so a correctly stored string still displays wrong. Retrofitting costs several times more.
It is what both audiences assess first. A principal reads the portfolio for channel conflict before discussing an appointment. A retailer reads it to gauge how much of its order book one supplier covers.
Context
Tell us what your operation runs on today.
Real feedback from the people we've proudly partnered with.
Sales Director |Cintas
United States
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
Founder & CEO |Moneteo
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
CEO |E-Commerce Platform
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
