ZelenaPijaca.ba
A domain-specific marketplace for local producers, food and agricultural supply.
ZelenaPijaca.ba takes proven marketplace foundations into a stricter vertical domain where producer identity, trust, category structure and operational clarity matter as much as listings. It is built as its own product, with dedicated producer verification, taxonomy and admin workflows rather than as a visual clone of Handmade.ba.
Product type
Vertical marketplace · local commerce
Status
Completed product
Astraealibra scope
Product strategy · marketplace architecture · full-stack development
Product identity
ZelenaPijaca.ba
Product in practice
A completed product on its own public domain.
ZelenaPijaca.ba is publicly available as a dedicated product for local producers. The proof is the active platform itself: a real domain, real user interface and a system that can be opened and inspected.
Domain
ZelenaPijaca.ba
Access
Publicly available
ZelenaPijaca.ba
https://zelenapijaca.ba
Functional scope
What the product is built to do.
Producer profiles and product listings organized around food and agricultural categories
Verified-producer workflow with explicit admin verification and revocation
Dedicated vendor and administration surfaces for marketplace operations
Domain-specific category taxonomy for produce, food, plants and related supply
Search, filtering and discovery across local producer inventory
Marketplace media, notifications and operational data flows
Foundations for future local-commerce and fulfillment workflows
System architecture
How the product is structured beyond the interface.
Marketplace experience
01A Next.js storefront provides producer discovery, product browsing and responsive commerce UX tailored to a local-food marketplace.
Marketplace backend
02A Medusa-based backend owns commerce and vendor logic while separate vendor/admin applications keep seller and operator workflows isolated from the public storefront.
Trust & discovery layer
03Custom producer-verification endpoints, explicit verification state and an idempotent domain taxonomy support trust, moderation and predictable discovery.
Infrastructure
04Vercel, Render, Neon/PostgreSQL, Redis, Cloudflare R2 and search infrastructure provide separated delivery, persistence, caching and media responsibilities.
Engineering highlights
The work that makes the system durable, testable and operable.
A verified-producer lifecycle implemented as product logic rather than a decorative badge
Idempotent category seeding for a large, domain-specific producer and food taxonomy
Separate storefront, backend and admin repositories to preserve clear operational boundaries
Reuse of marketplace principles without coupling the product to Handmade.ba branding or domain assumptions
Infrastructure split across database, cache, object storage, search and application hosting
Technology
Production stack and supporting infrastructure.
Current direction
Where the product is now.
The core product is functionally complete. The public storefront, backend and administration systems are built, including producer verification and domain-specific catalog structure. Further work can focus on content, operational launch and future enhancements rather than building the platform foundation.