Bagisto eCommerce Marketplace GDPR

Bagisto eCommerce Marketplace GDPR module extends your Bagisto marketplace, so that your sellers enjoy the same data-protection rights the European Union’s General Data Protection Regulation grants to your customers.

The GDPR is the EU law that governs data protection and privacy across the European Union and the European Economic Area. Bagisto already ships with customer-side GDPR tools. This module, therefore, adds the seller-side counterpart, and it also brings a site-wide cookie consent notice.

Once you install the module, a seller can export everything the marketplace holds about them, raise a request to update their data, or ask you to delete their account. Meanwhile, the admin reviews every request from a dedicated grid and moves it through Pending, Processing, Complete, or Declined. The module then emails the seller on every status change.

Note: This module is an add-on to the Laravel Multi Vendor Marketplace Module. Therefore, you must install Webkul Laravel Multi Vendor Marketplace first, and you must also switch the Marketplace module on, because the GDPR menus stay hidden while it sleeps.

Scope: the customer-facing GDPR screens (My Account >> GDPR on the storefront and Customers >> GDPR Data Requests in the admin panel) belong to Bagisto core, and their own configuration governs them. This module, in contrast, owns the seller data requests, the seller sign-up agreement, and the cookie consent notice.

If you’re looking to enable custom ring builder option on your Laravel store, then you can check the Laravel Custom Ring Builder Extension

• Sellers can ask you to update their data, or alternatively to delete their account altogether.
• Sellers can reach their data instantly, because the module downloads it as a PDF or renders it as an HTML page.
• That export covers the seller’s account information, address information, products, orders, and finally transactions.
• Sellers can track every request they raise, and they can also watch its current status, from their own panel.
• Admin can write agreement content and then force every new seller to accept it at sign-up.
• Admin can run a cookie notice across the storefront, and can additionally park it at the bottom left or the bottom right.
• Admin writes the description a shopper reads for each of the five cookie consent categories.
• Admin sees every seller update and delete request in one searchable, filterable grid.
• Admin moves a request to Pending, Processing, Complete, or Declined, either one at a time or in bulk.
• The seller receives an email as soon as they raise a request, and again on every status update.
• Switching the module off returns a 404 for every GDPR route and hides its menus, so nothing lingers half-live.

• First, unzip the extension and merge the “packages” folder into your project root directory.

• Then open bootstrap/providers.php and register the service provider at the end of the returned array, right after the Marketplace service provider.

use Webkul\MarketplaceGDPR\Providers\MarketplaceGDPRServiceProvider;

return [
    MarketplaceGDPRServiceProvider::class,
]

Next, open the root composer.json file and add the following line under ‘autoload >> psr-4’.

"Webkul\\MarketplaceGDPR\\": "packages/Webkul/MarketplaceGDPR/src"

• Finally, run the commands below to complete the setup.

composer dump-autoload

php artisan marketplace-gdpr:install

php artisan optimize:clear

That’s it, now just execute the project on your specified domain.

After you install the module, navigate to Configure >> Marketplace and open the module’s settings card (admin/configuration/marketplace/gdpr). This single screen drives everything the module offers, and it groups the fields into four sections.

General

Status – This toggle acts as the master switch. While it sleeps, the seller GDPR screens, the admin request grid, the sign-up agreement, and the cookie notice all stay dormant, and the module’s routes answer with a 404.

Seller Agreement

Enabled Seller Data Agreement – Turn this on to show a mandatory data agreement checkbox on the seller sign-up form. The two fields below appear only after you switch it on.

Agreement Checkbox Label – This text sits next to the checkbox on the seller sign-up form, and it accepts up to 100 characters. By default, it reads “I agree with the terms and conditions.”

Agreement Content – A rich-text editor holds the full agreement. The seller then reads it in a popup after clicking the link beside the checkbox.

Cookie Message Settings

Enabled Cookie Notice – Turn this on, and the storefront starts showing the cookie notice.

Cookie Block Display Position – Park the notice at the Bottom Left or, alternatively, at the Bottom Right of the screen.

Cookie Static Block Identifier – This heading crowns the cookie notice. It defaults to “Cookie Notice”, and the screen treats it as mandatory.

Your Cookie Consent Preferences

Here the admin writes the description a shopper reads for each cookie category on the consent preferences screen. Each of the five fields stays mandatory, though every one of them ships with a sensible default.

• Strictly Necessary
• Basic Interactions & Functionalities
• Experience Enhancement
• Measurement
• Targeting & Advertising

Every field on this screen follows the channel and the locale. Consequently, a multi-store or multi-language marketplace can present a different agreement, and different cookie wording, on each storefront.

Once you enable the cookie notice, every storefront page greets a first-time visitor with the notice below. It carries the heading you chose in the configuration, a short message linking to your Privacy Policy page, and finally three actions.

• Accept – stores the consent cookie and then dismisses the notice.
• Reject – dismisses the notice, but stores no consent cookie.
• Learn more and customize – opens the consent preferences screen instead.

On the preferences screen the visitor decides, category by category, what your store may keep. Strictly Necessary always stays on and resists every change, while the visitor toggles the other four freely. Save and continue then writes those choices and returns the visitor to the home page.

Note: the consent preferences screen sits behind the storefront customer guard. Therefore, a visitor who has not signed in lands on the login page first.

Once you enable the seller agreement, a mandatory checkbox appears on the marketplace sign-up form. Until the seller ticks it, the form refuses to register them.

Clicking the link beside the checkbox then opens a popup with the full agreement content the admin wrote in the configuration.

A logged-in seller opens GDPR Request from the seller panel menu, and lands on the Seller GDPR Data Request screen. It offers three actions in the page header, and it also lists every request the seller has raised so far.

Get Pdf – Downloads the seller’s complete data export as an A4 PDF. That export covers account information, address information, product information, order information, and finally transaction information.

Get Html – Opens the very same export as an HTML page in a new tab, especially for sellers who would rather read it in the browser.

Create Request – Opens a modal where the seller picks a Request Type and then writes a Message of up to 250 characters explaining what they want. Both fields stay mandatory.

• Update – ask the admin to correct or otherwise update the stored information.
• Delete – ask the admin to delete the account instead.

As soon as the seller submits, the module stores the request with the status Pending, and it then emails the seller a confirmation.

Request List – The grid below the header shows Id, Request Status, Request Type, Message, Created Date, and Updated Date. Furthermore, it supports search, sorting, and filters. On a phone, meanwhile, the screen shows those same records as cards.

To review what the sellers have raised, the admin goes to Marketplace >> Seller GDPR Data Request. The grid lists Id, Seller Id, Request Status, Request Type, Message, Created Date, and Updated Date. In addition, it offers search, sorting, and dropdown filters on both status and type.

The admin can also select several rows at once, and then use the mass actions to Delete them or to Update Status in bulk. Moreover, a bulk status update emails every seller it touches.

Each row carries an edit and a delete action too. Clicking the edit icon opens the request, where the admin sees the request type the seller chose alongside the message they sent. From there, the admin moves the Request Status to Pending, Processing, Declined, or Complete, and can also reply by editing the message. The request type itself stays read-only, because only the seller decides what they are asking for.

Saving the form emails the seller the updated status. Afterwards, the admin sees a confirmation message telling them whether that email actually went out.

So, that was much about the User Guide of Bagisto eCommerce Marketplace GDPR for any queries or doubts reach out to us at [email protected]. You can also raise a ticket at our HelpDesk System.

Please explore our Laravel Development Services and Quality Bagisto Extensions.