BookPound — A multi-vendor used book marketplace built for Nigerian readers

Nigeria had no dedicated digital marketplace for used books — and building one meant solving three problems simultaneously: enabling sellers to trade anonymously to protect their privacy, handling NGN payments natively, and managing commission settlement in a market where automatic payment splits are not straightforward.

BookPound came to Yielded Circle Tech with a clear market gap: Nigerian readers who wanted to buy and sell used books had no dedicated platform built for them. The informal market existed — people sold books via WhatsApp groups, Instagram pages, and physical meetups — but it was fragmented, risky, and hard to scale.

Building the platform itself was the starting point. But three specific problems made this project significantly more complex than a standard Magento implementation.

Problem 1 — Seller privacy: Many sellers did not want their real names visible to buyers on a public marketplace. This was not vanity — it was a legitimate concern about privacy, safety, and the social dynamics of selling personal property online in Nigeria. A standard Magento multi-vendor implementation would expose seller identities by default. We needed a system that generated consistent, believable pseudonyms for each seller — the same pseudonym every time, across all their listings and transactions — without exposing their real identity at any point.

Problem 2 — NGN currency: Magento's default currency handling did not cleanly support Naira at the configuration level required. Setting up NGN as the functional currency across the storefront, checkout, reporting, and admin panel required custom configuration work that went beyond standard setup.

Problem 3 — Commission management: Paystack's default settlement behaviour moves funds to the merchant account on a T+1 basis — meaning money goes to the platform automatically. But BookPound needed to retain a commission on each sale and pay out the remainder to the seller. This required integrating Paystack's Transfers API and building a manual settlement layer that calculated seller payouts, deducted commission, and initiated transfers on a managed basis rather than relying on automatic settlement.

We built BookPound on Magento 2.4.8 with the Webkul Multivendor extension as the marketplace foundation, deployed via Docker on a DigitalOcean Droplet with MySQL, Elasticsearch, and Redis in the infrastructure stack.

Seller privacy — custom pseudonym module: We built a custom Magento module — BookPound_VendorPrivacy — that intercepts the seller registration process and generates a consistent pseudonym for each seller using a MySQL BEFORE trigger. The pseudonym is generated at registration, stored against the seller record, and used in place of the seller's real name across all public-facing parts of the platform — listings, order communications, and seller profile pages. The same pseudonym is used every time, so sellers have a consistent public identity without their real name ever being exposed.

NGN currency: We configured Naira as the platform's functional currency across the full Magento stack — storefront display, checkout flow, admin reporting, and the Webkul vendor dashboard — including custom cron configuration for currency rate management.

Commission management: We integrated Paystack with manual settlement enabled — turning off automatic T+1 transfer so funds accumulate in the platform account. We then built a commission management layer using Paystack's Transfers API: when a sale is confirmed, the system calculates the seller's payout (sale price minus commission), initiates a Paystack transfer to the seller's registered bank account, and logs the transaction for admin reconciliation.

Email infrastructure: We configured AWS Simple Email Service (SES) as the transactional email provider — handling order confirmations, shipping notifications, seller alerts, and account management emails. This included full DNS verification, DKIM setup, and bounce and complaint handling.

The most important phase of the BookPound build was correctly diagnosing which problems had off-the-shelf solutions and which required custom engineering. Getting that wrong in either direction — over-engineering a solved problem, or reaching for a plugin where custom code was needed — would have cost time and introduced fragility.

Platform selection: Magento 2.4.8 with Webkul Multivendor was the right foundation for the marketplace requirements. The extension handled the core multi-vendor flows — seller onboarding, product listing, order routing — so we could focus engineering effort on the custom problems.

Custom module development: The VendorPrivacy module was the most novel piece of engineering in the project. Using a MySQL BEFORE trigger to intercept and modify the seller record at the database level — rather than at the application layer — gave us a clean, reliable mechanism that worked consistently regardless of how the seller record was created or modified.

Payment architecture: The decision to use Paystack's manual settlement mode and Transfers API rather than automatic settlement was the correct call for the commission model. It gave the platform operator full control over payout timing and amounts, with a clear reconciliation trail.

Infrastructure: We selected a DigitalOcean Droplet at 4GB RAM as the deployment target — appropriately sized for the initial traffic volume with a clear upgrade path as the platform grows.

BookPound reinforced a principle that applies to every platform-based project: the framework handles the common case, and your value as a development team is in how you handle the uncommon cases.

Magento handled the marketplace. Webkul handled the vendor flows. But seller privacy, NGN currency depth, and Paystack commission management were all problems the platform did not solve — and those were exactly the problems that made BookPound different from every other book website.

The instinct when using a platform is to find a plugin for every problem. Sometimes that is right. But the VendorPrivacy module needed to be custom-built because no plugin could provide the database-level consistency the privacy model required. Knowing when to extend, and when to build, is one of the most important technical judgements in platform development.