Multivendor Seller App for WooCommerce documentation

What you bought: three parts that work together

The plugin detects your marketplace plugin by itself:

1. Unzip the package you downloaded. Inside are multivendor-app-for-woocommerce-plugin.zip and flutter-app-source.zip. Do not unzip these two.
2. In WordPress open Plugins → Add New → Upload Plugin, choose multivendor-app-for-woocommerce-plugin.zip, press Install Now, then Activate.
3. Open Settings → Seller App. If you see the page with six tabs (App Config, Branding, SMS & WhatsApp, Push Notifications, Test Notifications, App Builder), the plugin is ready.
4. Check Settings → Permalinks: anything except “Plain” is fine. Press Save Changes once if the app cannot reach your store.

App Config

Branding

Primary colour, support email and support WhatsApp number. The app can read them from /app-config.

SMS & WhatsApp

Switch on Enable Automated Alerts, choose a provider, paste the key (and secret), the sender name and edit the message. You can use {order_id}, {total}, {store_name}, {customer_name}, {payment_method} and {order_date}. The seller gets this text when an order that contains their products is placed. The seller’s phone number comes from the billing phone on their WordPress profile.

Push Notifications

Test Notifications

Search a user, type a message and press Send Test Push or Send Test SMS. The answer from Firebase or your SMS provider is shown on the page, which makes problems easy to find. The user must have logged into the app once to receive a push.

A. Create the Firebase project

1. Go to console.firebase.google.com and sign in with a Google account.
2. Press Add project, type a name (for example “Acme Sellers”) and finish the wizard. You can turn Google Analytics off.

B. The file for the app: google-services.json (Android)

1. In your project press the Android icon (“Add app”).
2. Android package name: type the unique name of your app, for example com.acme.sellers. Write it down: use exactly the same name in the App Builder (chapter 9).
3. Press Register app, then Download google-services.json. Keep it for chapter 9 or 10. Skip the remaining Firebase screens.

C. The file for your store: a service account key

1. In Firebase press the gear icon → Project settings → tab Service accounts.
2. Press Generate new private key and confirm. A .json file downloads.
3. Open it in a text editor, select everything and copy.
4. In WordPress open Settings → Seller App → Push Notifications, paste into the box and press Save Settings.

D. iPhone only

Also add an iOS app in Firebase (use your bundle ID), download GoogleService-Info.plist and upload an Apple APNs key under Project settings → Cloud Messaging. Details are in chapter 10.

Test it

Log into the app on a phone, then open Test Notifications, pick that user and press Send Test Push. The phone should ring within seconds.

Log in

1. Open the app and type your WordPress username and password. Store admins use their admin login.
2. Allow notifications when the phone asks.
3. You stay logged in on this phone until you press Sign Out (or 90 days pass, or the role is removed). Logging in on a second phone does not log out the first.

Dashboard

Total earnings (store admins see the total sales of the whole store), number of orders, active, pending and offline products, and products that are out of stock. Pull down to refresh. The bell shows alerts such as out-of-stock or low-stock products and products waiting for approval. A “Store admin” badge shows when you are logged in as admin.

Orders

• Search by order number (admins also by customer name or email) and filter by status.
• Open an order to see the customer, payment method, products with photos and the total.
• Change the status with the Order Status box at the top (it is a drop-down list), for example from Processing to Completed. Sellers can use Processing, On hold, Completed and Cancelled. Only store admins can use other statuses such as Refunded.

Inventory (products)

• Search, filter by status, and use Out of stock from the dashboard.
• Tap the round + at the top right to add a product: name, prices, sale price, description, categories, stock quantity or stock status, a main photo and gallery photos from the camera or gallery.
• Open a product and use the pencil to edit it or the bin to delete it. Deleted products go to the trash.
• Sellers only see and change their own products; store admins see all.

Profile and store settings

Edit the store name, phone, address, logo and banner, business hours and the shipping, refund and cancellation policies.

When a customer places an order, the plugin finds which sellers own products in it and sends each of them a push notification (“New Order Received! Order #123 total is …”) and, if switched on, an SMS. Store administrators are notified of every order. Each order is announced only once.

A seller’s phone must be registered: the app does this by itself after login and every time the app opens. A phone belongs to one account: if somebody else logs in on the same phone, the previous account stops receiving alerts from it. Signing out also stops alerts for that phone.

Before you start

• Your purchase code.
• Your app icon (square PNG, 1024×1024), a logo and a splash image.
• The google-services.json file from chapter 6, made for the package name you will type below.

Step by step

1. Open Settings → Seller App → App Builder.
2. Step 1. Check your website address (https, no slash at the end), paste your purchase code and press Connect & load my app. The green “Connected” sign appears. Your code stays on your server and is not shown again.
3. Step 2. Type the App name (shown under the icon), the Package name (the same one you gave Firebase, for example com.acme.sellers) and your email. The download link is sent there.
4. Step 3. Choose the icon, logo and splash images (they upload as soon as you pick them), choose the splash colour and upload google-services.json.
5. Step 4. Choose APK (install straight on a phone) or App Bundle (for Google Play). Press Save details, then Start Android build.
6. Wait for the email (usually a few minutes; builds are queued). Open the link on the phone to download and install the APK.

Good to know

• The builder makes Android apps. For iPhone use the source code (chapter 10).
• Every purchase code can build one app. To change the name, icon or screens later, save the form again and press Build again.
• What is sent to the build server: your site address, purchase code, app name, package name, your email and phone, splash colour, your three images and the Firebase file. No store passwords or WooCommerce keys are needed.
• Only administrators can use this tab; every request is protected by a security token.

Requirements

• Flutter 3.41 or newer (flutter doctor green), Android Studio for Android, Xcode and CocoaPods for iPhone.

1. Open the project and point it to your store

unzip flutter-app-source.zip -d seller_app && cd seller_app
flutter pub get

# run on a connected phone or emulator
flutter run --dart-define=API_DOMAIN=https://yourmarketplace.com

Or change the default permanently in lib/core/constants/app_config.dart:

class AppConfig {
  static const String siteUrl = String.fromEnvironment(
    'API_DOMAIN',
    defaultValue: 'https://yourmarketplace.com',   // <- your store, no slash at the end
  );
  static const String apiBaseUrl = '$siteUrl/wp-json/multivendor-seller/v1';
}

2. Add your Firebase files

• Android: android/app/google-services.json (the Gradle plugin switches on automatically when the file exists).
• iPhone: ios/Runner/GoogleService-Info.plist; open ios/Runner.xcworkspace in Xcode and drag it into the Runner group if it shows in red.

3. Name, package and icons

# unique app id (must match Firebase)
dart run change_app_package_name:main com.acme.sellers

# replace assets/images/icon.png (1024x1024) and assets/images/splash.png, then:
dart run flutter_launcher_icons
dart run flutter_native_splash:create

The app name shown on the phone is in android/app/src/main/AndroidManifest.xml (android:label) and ios/Runner/Info.plist (CFBundleDisplayName).

4. Sign and build (Android)

# create a signing key once and keep it safe
keytool -genkey -v -keystore ~/acme-sellers.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload

# android/key.properties
storeFile=/Users/you/acme-sellers.jks
storePassword=...
keyAlias=upload
keyPassword=...

In android/app/build.gradle.kts read these values in a signingConfigs { create("release") { … } } block and use it in buildTypes.release instead of the debug key (the file has a comment where). Then:

flutter build apk --release --dart-define=API_DOMAIN=https://yourmarketplace.com          # APK to test
flutter build appbundle --release --dart-define=API_DOMAIN=https://yourmarketplace.com     # AAB for Google Play

5. iPhone

cd ios && pod install --repo-update && cd ..
flutter build ipa --release --dart-define=API_DOMAIN=https://yourmarketplace.com

In Xcode choose your Team, set a unique Bundle Identifier (the same as in Firebase) and keep the Push Notifications capability. Upload an APNs key in Firebase.

Where things are

Base address: https://yourstore.com/wp-json/multivendor-seller/v1. Everything except /login and /app-config needs the token from login, sent as Authorization: Bearer … (or in the header X-Seller-Token). Tokens last 90 days; each phone has its own (up to 5 per user).

Try it

# log in (admin works too)
curl -s -X POST https://yourstore.com/wp-json/multivendor-seller/v1/login \
  -H 'Content-Type: application/json' \
  -d '{"username":"admin","password":"your-password"}'
# -> {"success":true,"token":"MXx8…","user_id":1,"is_admin":true,...}

# list orders
curl -s 'https://yourstore.com/wp-json/multivendor-seller/v1/seller-orders?status=processing' \
  -H 'Authorization: Bearer MXx8…'

# complete an order
curl -s -X PUT https://yourstore.com/wp-json/multivendor-seller/v1/seller-orders/123 \
  -H 'Authorization: Bearer MXx8…' -H 'Content-Type: application/json' -d '{"status":"completed"}'

Let another role use the app

// functions.php or a small plugin
add_filter( 'mvs_app_roles', function ( $roles ) {
    $roles[] = 'my_custom_vendor_role';
    return $roles;
} );

• Every request needs a login token (except login and the public app settings). A seller can only read and change their own products, orders, profile and photos; the server decides, not the app.
• Tokens are random, kept as a one-way hash, last 90 days, are per phone, and stop working at once when the user is logged out, deleted or loses the role.
• Login attempts are limited (5 wrong passwords, then 15 minutes).
• Uploads must be real JPG, PNG, GIF or WebP images; prices, statuses and stock values are checked.
• Sellers cannot refund or trash orders from the app.
• The App Builder tab and every admin action need an administrator and a security token; nothing is available to visitors.
• The SMS and Firebase secrets stay on your server. The SMS secret is not printed back into the settings page.
• Tell your sellers in your privacy policy what the app handles (orders, customer names and phone numbers, product photos).

Updating

Upload the new plugin zip with Replace current with uploaded; settings stay. Build a new app version (chapter 9 or 10) and raise Force App Update when you want everybody to update.

If you used “MultiVendor Seller App for WooCommerce” 1.0.0 and “Taqnix App Builder”

• This plugin replaces both. Deactivate and delete “Taqnix App Builder”; its builder is now the App Builder tab here (enter your purchase code once).
• The old plugin file had a stray apostrophe in its name. Delete the old plugin folder completely, then upload this one.
• Everybody has to log in again once. Login tokens are stored differently now (per phone, with an expiry), so old sessions end.
• Settings are kept. The new options (maintenance message, new-product review, update link) start with safe defaults.

Removing

Deactivate and delete the plugin. Sellers, products and orders stay. The plugin’s settings are removed.

Installation help and bug fixes are included for 6 months, with lifetime updates. Contact us through the marketplace item page where you bought the package. Please include your store address, which marketplace plugin you use, what you did, and what you saw (a screenshot helps).