🌐 Language: 🇻🇳 Tiếng Việt · 🇬🇧 English (current)

Release history — MultiVendor

Introduction

This page lists the MultiVendor plugin versions and the notable changes in each, so a marketplace owner knows which version they run and what an upgrade brings. Feature details are in the Marketplace overview on gp247.net.

Version 1.0.1

• The shop path moved from /vendor to /shop. The old path collided with a real folder on the server (public/vendor/, where libraries put their static files), so the web server answered 403 before the request ever reached S-Cart and the shop directory could not be opened. The directory is now at /shop, a shop page at /shop/{code}. Sites already on the old path: set up 301 redirects from /vendor/{code} to /shop/{code} so search rankings survive; do not pin the old value back in .env — the 403 comes back with it. If you want a different path, pick a name that is not a folder under public/ (avoid vendor, storage, GP247).
• On the free edition, Pro switches now show what is actually running. They used to render the stored value, so a site that once ran Pro and switched it off saw ticked boxes and Vendor order actions reading "Confirm + ship" while the free edition only runs "Shipping status only". The value you saved is not lost — switch Pro back on and it returns. The lock strip is tidier too: a single badge on the same line as the setting.
• Sample data brings the review plugin with it. php artisan gp247:vendor-sample now settles Product Rating & Review so shop pages have their Reviews tab: already installed is left alone (only switched on if it was off), not installed gets installed from the plugin folder or downloaded from the library. If it cannot be installed (no internet, a copy that needs a license) the command still finishes seeding and prints the command to run afterwards. Use --skip-rating if you manage plugins yourself.
• The detailed guides moved to gp247.net. The plugin folder keeps only its README (and this page); setup, operations and customisation now have one source, always the current version: gp247.net/en/docs/plugin-multi-vendor.

Version 1.0.0 — first public release

• Compatibility: gp247/core 3.0, gp247/shop 3.x (S-Cart 3.x). Requires Livewire.
• Packaging: a free MultiVendor edition (up to 3 shops) and a paid MultiVendorPro unlock for everything else. Pro installs on top of Free; nothing is reinstalled.
• The free edition always shows what Pro adds: the menu and the sidebar still list the Pro screens; opening one explains the feature and lists the rest. After installing Pro those same entries open the real screens — no menu rearranging.

The marketplace model

• Many vendors on one domain: a shop lives at /shop/{code}, a directory at /shop, the cart is split per shop and each shop gets its own order. The marketplace collects the money and pays each shop its share per period.
• The shop page carries a cover, logo, banners, Products / Reviews / About tabs and a search inside the shop.
• Public trust signals on the shop page: complaint rate, typical handling time, share of complaints and reviews answered — over the last 90 days, hidden until a shop has sold enough for the figures to mean anything.
• A shop name with an icon on product cards and the product page, linking to that shop.

For the marketplace owner

• Manage shops, vendor accounts and marketplace settings; a moderation queue for shops, products and identity profiles, where a rejection needs a reason and is written to an audit trail.
• Commission per shop, resolved in order: the shop's own rate, then its plan, then the marketplace rate.
• Payout runs per period with payout methods, an Excel statement, and a bank instruction file per batch plus one-click settlement of the whole batch against a single bank reference. Only a system administrator can download the file, and every download is logged.
• Clawback after payout when an order is refunded or cancelled, netted into the next period.
• Vendor identity verification with an encrypted profile, a verified badge, and an option to require it before products go live and money is released.
• A disputes desk in two steps: the shop answers first, the marketplace decides, and a refund is written straight into the order's ledger.
• Vendor plans: product cap, own commission, periodic fee netted from the payout, and a switch for which plans shops may pick themselves.
• Commission reports per shop and per period, on two explicit bases, exported to Excel.

For a shop

• Its own admin area at /vendor_admin: dashboard, products, categories, banners, suppliers, shop details, payout history; self-registration when the marketplace allows it.
• Order handling: move an order through the allowed states, record a tracking code, print a delivery note.
• Type an order for a customer, with the unit price filled in from that customer's price group and still editable.
• Its own price groups: a discount percentage per customer group and a mapping of customers into them. A signed-in customer sees their own price everywhere in that shop, and that price is never shown to anyone else.
• Answer the reviews of what it sells; approving, rejecting and deleting a review stay with the marketplace.
• Pick its own plan from the ones the marketplace published, with the fee netted from the next payout.
• Configure the plugins the marketplace opened to shops (shipping, promotions); payment gateways are always the marketplace's to configure.

For customers

• Buy from several shops in one cart.
• Quick bulk ordering per shop: browse by category, paste a list of SKUs, reorder a past order, export a quote to Excel.
• Open a dispute from the order page and follow where it stands.

Notifications

• E-mail to a shop on a new order, on approval, on payout, on a clawback, on an identity decision, and at each stage of a dispute.
• E-mail to the marketplace when a shop or a product is waiting for approval.

Technical

• Both the marketplace and shop admin areas run on GP247 v2 Livewire + TailAdmin — no jQuery, no legacy CSS framework.
• Vendor accounts are separate from admin accounts behind their own guard; every vendor screen is fenced to the shop that is signed in.
• Vietnamese and English. Events Creating/Created VendorStore|VendorUser and Paying/Paid Vendor are available for extensions.
• Runs on restricted hosting: no cron, no queue, no websocket required.
• Mutually exclusive with the MultiStore plugin — two different business models over the same store table.

A note on version numbers

This is the first public release. The 1.1 to 2.6 milestones that appear in internal development records are internal build milestones and were never released.