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

MKP — Marketplace template for S-Cart (GP247 3.x)

Introduction

MKP is a marketplace-style storefront theme for S-Cart 3.x — a paid template, used under a license GP247 issues for your domain. It ships what shoppers of a marketplace expect to see: many stores, the seller of each product, reviews, and a tidy purchase flow on phones. This document is for S-Cart site owners: what MKP does, how it differs from the default template, how to install it and how to customise it.

Version 1.0 · requires gp247/core 3.0 and gp247/front; gp247/shop recommended.

🔗 See the demo: m-vendor.s-cart.org · Buy a license and learn more: gp247.net — Template Marketplace MKP

What the template does

Shoppers find products faster. Right under the banner, the home page puts flash sales (with the plugin), the trust strip and promoted products first, then the category grid, new stores (with the plugin) and new products. On phones, listing pages show products on the first screen and the filter folds away.

Shoppers trust sellers more. Every product says who sells it: the store name on the product card, a Seller card on the product page (logo, rating, a link to the store), and star ratings next to the product name. The home trust strip only states what the site really offers.

Buying on a phone takes fewer steps and fewer mistakes. A sticky buy bar on the product page, a cart grouped by store that says each store checks out separately, and a checkout that shows an order summary (which store, how many items, how much) from the address step on.

You change the look without losing features. MKP works with the same plugins as the default template, and when assigned to a store it places the home-page blocks of the active plugins again.

Details

Home page and finding products

• Top bar (hotline, language, currency, entry points Stores and Sell with us), search box with a category menu, Account / Wishlist / Cart with counters.
• Home page built from layout blocks: large slider + 2 side banners, trust strip, promoted products, category grid with sub-categories, new products, mini banners, news, brands (logo with name), newsletter sign-up.
• 5-column product grid on wide screens; sub-category chips and a folding filter on phones.

Product page and seller

• Seller card: logo, name, store rating, View store button; the seller is named once.
• Price with a -x% badge when discounted; grouped products list each member with image, name and price.
• Quantity field with −/+ buttons, and a sticky buy bar on phones while the Add to cart button is out of view.
• Real sharing: Facebook, X, copy link, and the phone's share sheet where the browser supports it.
• Long descriptions fold with Show more / Show less.

Cart and checkout

• The cart is grouped by store, each with its own subtotal and checkout button; Clear cart appears once (it removes every store's items).
• An empty cart offers a way back to shopping.
• Multi-step checkout; the steps before confirmation show an order summary that opens to list every line.

Phones and accessibility

• Bottom navigation: Home, Categories, Stores, Cart, Account.
• Text colours meet WCAG AA contrast; buttons and icons on phones are at least 44px.
• Right-to-left (RTL) languages supported.

Compatibility

• Works with the same plugins as the default template: product reviews (ProductRating), vouchers (ShopDiscount), captcha (GoogleCaptcha), social login (LoginSocial), flash sale (ProductFlashSale), news (News), payment / shipping.
• Multi-vendor (MultiVendor) and multi-store (MultiStore): store name on product cards, a new-stores block, and the plugin's store pages rendered in MKP's style.
• Cart, filter, product card and checkout run on gp247/shop's Livewire components — add to cart, change quantities, filter and sort without a page reload.
• No jQuery / Bootstrap: pre-compiled Tailwind CSS, interactions with Alpine (bundled with Livewire).
• Runs on ordinary shared hosting: no Node, cron or queue worker needed to use it.

How MKP differs from the default template (GP247Front)

Switch between the two at any time on the store management screen; products, orders and customers are untouched.

Assigning the template to a store

flowchart LR
    A[Install MKP] --> B[Assign MKP to a store]
    B --> C[Old template's blocks removed<br/>plugin blocks included]
    C --> D[MKP places home, left-column<br/>blocks and sample banners]
    D --> E{Which plugins are active?}
    E -->|ProductFlashSale| F[Place the flash sale block again]
    E -->|MultiVendor| G[Place the new-stores block again]
    E -->|none| H[Done]
    F --> H
    G --> H

Assigning MKP again never duplicates blocks. A plugin installed after MKP is assigned places its own block as usual.

Shopping on the marketplace

flowchart LR
    A[Shopper adds products<br/>from several stores] --> B[Cart grouped<br/>by store]
    B --> C[Checkout<br/>for one store]
    C --> D[Address<br/>+ that store's order summary]
    D --> E[Shipping / payment<br/>if the store enables them]
    E --> F[Confirm and place order]
    F --> G{Items from another<br/>store left in the cart?}
    G -->|yes| C
    G -->|no| H[Done]

Requirements

• S-Cart 3.x with gp247/core 3.0 and gp247/front.
• gp247/shop for cart, products and checkout (without it, pages and news still work).
• Runs on ordinary shared hosting.

License

• After purchase, GP247 issues an MKP license bound to your site's domain (the domain in APP_URL of .env).
• This license is not the free API License that connects your site to the GP247 library (gp247:ext-register-license): the API License only opens the connection, the MKP license is what lets you download and update the template.
• Downloading a new version (update) needs a license that is still valid for that domain; if it has expired or the domain does not match, the installer stops and says why.
• Licensing, updates and support go through the GP247 paid channel that delivered the template to you.

Installation

1. Admin → Extensions → Templates: upload the zip you received with your purchase, or install from the GP247 library with your license, then click Install.
2. Assign the template to a store on the store management screen. MKP creates its layout blocks and sample banners (names end with (MKP)).

Manual install: copy the MKP folder into app/GP247/Templates/ and app/GP247/Templates/MKP/public/ into public/GP247/Templates/MKP/, then follow steps 1–2.

The old Bootstrap MKP (for GP247 1.x) cannot be upgraded in place to this version — uninstall it and install this one.

Install from the command line (CLI, gp247 3.x)

Open a terminal in the site's root folder and run:

# 1) Once per site: register the (free) API License to connect to the GP247 library
php artisan gp247:ext-register-license

# 2) Download MKP from the library and install it with the license you received on purchase
php artisan gp247:ext-install --type=template --key=MKP --paid --license=<your-license>

• <your-license> is the MKP license GP247 issues for your domain after purchase — not the free API License from step 1.
• Before step 1, make sure APP_URL in .env is the site's real domain (not http://localhost); both licenses are bound to it.
• Paid extensions install one key at a time: do not combine MKP with other keys in the same --paid command.
• If app/GP247/Templates/MKP already exists (unzipped from the purchased zip), the command installs in place without downloading and without --paid.
• To move to a newer version: php artisan gp247:ext-update --type=template --key=MKP (needs a valid license — see License).
• Add --json for machine-readable output (scripts/CI).
• After installing, you still assign the template to a store.

Customisation

Updating MKP overwrites the template's files. Before updating, back up app/GP247/Templates/MKP and note the files you changed so you can apply them again afterwards.

After changing CSS/JS or adding new Tailwind classes in Blade, rebuild (run from the site's root folder, Node required):

npx tailwindcss@3 -c app/GP247/Templates/MKP/resources/assets/tailwind.config.js -i app/GP247/Templates/MKP/resources/assets/css/app.css -o app/GP247/Templates/MKP/public/css/app.css --minify

cp app/GP247/Templates/MKP/resources/assets/js/app.js app/GP247/Templates/MKP/public/js/app.js

then copy public/css and public/js into public/GP247/Templates/MKP/.

A Tailwind class that appeared nowhere at build time has no effect until you rebuild.

Layout blocks MKP creates when assigned to a store

The category_store_left block (a store's categories) is not placed by default because the store page already has its own category chips; place it by hand in Admin → Layout blocks if you want it.

Banner types used: banner-left (slider), banner-right, banner-mini, banner-special.

Documentation

Questions & answers (Q&A)

Q1: My site has a single owner — can I use MKP?

→ Yes. The marketplace parts (Seller card, Stores entry points, new-stores block) only appear with the MultiVendor or MultiStore plugin; without them MKP is a regular storefront.

Q2: Do I lose data switching from the default template to MKP?

→ No. Products, orders, customers and banners stay. Only the old template's layout blocks are replaced by MKP's.

Q3: I rearranged the blocks — will assigning MKP again overwrite them?

→ No. MKP only adds missing blocks; it never duplicates or changes existing ones.

Q4: I added a Tailwind class in a Blade file and nothing changed?

→ MKP's CSS is pre-compiled. New classes only work after a rebuild (see Customisation).

Q5: How is the MKP license different from the API License?

→ The API License (free, gp247:ext-register-license) only connects your site to the GP247 library. The MKP license is what you buy; it is bound to your domain and used when installing with --paid --license=… and when updating.

Q6: An update fails with a license error?

→ Check that APP_URL is the domain the license was bought for and that the license is still valid. Contact the GP247 paid channel that delivered the template to renew it or move it to another domain.

Q7: How do I change the wording?

→ Shop-wide texts are edited on the language screen in the admin; MKP's own texts live in the template's Lang/<language>/lang.php.