iBuilder Market - Multi-Vendor for WooCommerce

Turn WooCommerce into a multi-vendor marketplace: digital downloads with license keys, tiered services, commissions, payouts.

  • No license key or activation
  • Readable, editable source
  • Documentation in the zip
  • Translation ready
$79 one-off

Bought once, used on as many of your own sites as you like.

This listing is not published yet — the button goes to the seller profile.

A marketplace that handles what happens after the sale.

Plenty of multi-vendor plugins let several sellers list products. This one also issues license keys for the software they sell, keeps those keys in step with their GitHub releases, prices tiered services, records the commission on every line item, voids it when an order is refunded, and tracks what you owe each vendor.

No license key for this plugin. No activation. No phone-home.

Nothing to register and no remote check of any kind.

Worth being clear about, because it looks contradictory in a feature list: this plugin issues license keys. That is a feature your *vendors* use for the software they sell to *their* customers. There is no licence check, no activation and no domain lock on you.

Vendors stay out of your admin

A visitor applies through a front-end form. Approval is manual or automatic. On approval they get a deliberately narrow role that grants a front-end dashboard and nothing in wp-admin — listings, orders, earnings, store profile, payout details, all without ever seeing your admin. Each vendor gets a public store page with “Sold by” attribution across the shop.

Digital downloads with real licensing

A downloadable listing issues a license key on purchase with a per-license activation limit. The software being sold calls a REST API to activate, deactivate and validate:

“ POST /wp-json/ibuilder_market/v1/license/activate body: license_key, instance POST /wp-json/ibuilder_market/v1/license/deactivate body: license_key, instance GET /wp-json/ibuilder_market/v1/license/validate?license_key=... “

instance is whatever identifies one installation, so the limit counts machines rather than downloads, and a customer moving to a new laptop releases the old seat instead of burning one.

GitHub release sync — the part nobody else does

A vendor binds a listing to a GitHub repository and maps asset labels to filename globs. The downloadable files, version and changelog then follow the latest published release, checked daily.

The detail that matters: downloads are addressed by a stable label, not by filename. An installer that carries its version in the name — Tool_1.4.2_x64-setup.exe — keeps the same WooCommerce download ID from release to release, so existing customers keep working download permissions. Re-uploading a zip by hand breaks them every time.

Tiered services alongside products

Basic, Standard and Premium packages per service listing, each with its own price, description and delivery time. Tier prices are recomputed on the server at add-to-cart and at checkout, so a price edited in the browser cannot take effect.

Commissions that stay correct

A global rate with per-vendor overrides, recorded per line item when an order completes and voided automatically on refunds and cancellations — so a refunded sale does not leave a payable behind for you to spot three weeks later. Vendors store a PayPal email or Stripe account ID; you review pending earnings and mark them paid.

The plugin does not move money, and that is deliberate. It records what is owed. Paying happens in PayPal or Stripe, by you. A plugin holding payout credentials and initiating transfers would be a far larger liability on your site than a ledger is.

Bundled extra: a pay-per-use tools module

Dormant until you give it an API key, and you can sell a marketplace without ever switching it on. It sells WooCommerce credit packs and spends credits per run, with six tools that produce clean .docx and .xlsx: RFI drafting, submittal-log review, G702/G703 pay-application assembly, cost-exposure reporting, meeting minutes and daily reports. They call the Anthropic API with your key.

One filter registers your own tools instead, so the credits mechanism is reusable for any pay-per-run service — this is the piece to look at if you want metered AI features on a site and do not want to build the billing.

Built to be worked on

  • Every front-end template is overridable from your theme: drop a copy in your-theme/ibuilder-market/ and your version loads instead. Overrides survive updates.
  • Thirteen documented actions and filters: vendor lifecycle, license issuance, commission rate and recording, release sync, template resolution, tool registration.
  • WooCommerce HPOS (custom order tables) declared compatible.
  • Translation-ready, with every class, option, hook and CSS class carrying the product’s prefix.
  • No branding of ours anywhere — no logo, no credit line, no link to remove.
  • No bundled third-party code at all. Every PHP, JS and CSS file is original, and nothing loads from a CDN.

Requirements

WordPress 6.2+, WooCommerce 8.0+, PHP 7.4+, pretty permalinks. Full documentation ships inside the zip.

A policy note, not a feature note

If the software your vendors sell is GPL, MPL or Apache licensed, a license key cannot restrict rights those licences have already granted. Price a tier on what the buyer *gains* — support scope, update window, priority — not on what is withheld from the software. The plugin gives you the mechanism; the policy is yours to get right.

What it talks to

Every external service this plugin can contact is named in its readme.txt, under "External services", with what is sent and why. Where a service is optional it takes your own API key, and leaving the key blank leaves the feature off rather than breaking the plugin.

All eight plugins