DataFirefly B2B Team — Documentation
Install, configure and use multi-user B2B accounts: companies, roles, hierarchical approval, budgets and payment on account.
Overview
DataFirefly B2B Team turns a PrestaShop customer account into a real B2B organization: a company groups several buyers, each with a role, a budget and an authorization threshold. Orders that exceed a buyer’s authorization go through a hierarchical approval chain before they are created.
The module complements dfb2bquote (B2B quotes) and dfgroupassign (VIES validation): it acts as the organization hub of the B2B account.
Installation
- Drop the
dfb2bteamfolder into your shop’s/modules/directory, or install the ZIP archive from Modules > Module Manager. - Click Install. The module automatically creates its tables, two order states, five system roles, two default approval tiers and the admin tabs under Customers > B2B Team.
- Clear the PrestaShop cache if needed from Advanced Parameters > Performance.
Key concepts
Company
A company represents a customer organization. It has an owner customer (the administrator), an associated customer group that drives catalogue and pricing, a credit limit and options: payment on account, required purchase order, address restriction and catalogue restriction.
Member
A member links a customer to a company, with a role, an optional budget and a personal authorization threshold. In this version, a customer belongs to a single company.
Role
A role defines permissions and an approval level. Five system roles are provided and cannot be deleted; you can create your own roles.
Roles and permissions
Each role combines four permissions and an approval level:
- Order: place orders.
- Approve: clear pending requests.
- Manage: administer the company’s members, budgets and settings.
- View accounting: see the outstanding balance and invoices.
- Approval level: the higher it is, the higher the tiers the role can clear. A value of 0 means no approval power.
Provided roles: Administrator (level 9), Approver (level 5), Buyer (level 0), Accounting and Read only.
Hierarchical approval
An order requires approval when one of these conditions is met: the member’s budget is exceeded, the amount reaches their personal authorization threshold, or the amount matches one or more workflow tiers.
Workflow tiers
Each tier defines a minimum amount, a sequence level and the role level required to clear it. Tiers can be global (valid for all companies) or company-specific, which then take precedence over global tiers. Two global tiers are created on installation: from €1,000 a Manager (level 5), from €5,000 the Direction (level 9).
Flow
When approval is required, the buyer submits the order from the checkout. A request is created with a frozen cart snapshot; no order is created at this stage. Approvers are notified by email and handle the request from My account > Approvals. On final approval, the order is created with the “B2B – Payment on account” status, then the member’s budget and the company’s outstanding credit are consumed.
The frozen snapshot guarantees that prices and quantities do not drift between submission and approval.
Budgets and departments
Each member can have a capped budget, automatically reset every month, quarter or year. A budget of 0 means unlimited. Departments, or cost centers, group members and track spending per unit.
Payment on account and purchase order
If the company allows payment on account, its buyers can order within the available credit (credit limit minus used credit). The order is created unpaid, with the “B2B – Payment on account” status, for later invoicing. A purchase order (PO) number can be made mandatory at the company level.
Quick order and shared lists
Quick order lets you add many products to the cart by reference (SKU), with instant lookup. Shopping lists, private or shared with the whole company, reload into the cart in one click — ideal for recurring reorders.
Audit log and reporting
Every action — submission, approval, refusal, member addition — is recorded in an immutable audit log, with timestamp and IP address, available under Customers > B2B Team > Audit log. The approvals dashboard shows the key metrics: pending, approved and refused requests, approval rate and value pending.
Strict payment restriction
A module cannot reliably hide other modules’ payment methods at checkout. To force B2B members to use only the approval or payment-on-account flow, restrict the payment methods of the company’s customer group under Payment > Preferences.
FAQ
Does the module replace dfb2bquote?
No. B2B Team handles the organization, roles and approval; dfb2bquote handles quotes. The two are complementary and work together.
Is an order created before approval?
No. The order is only created on final approval, from the frozen cart snapshot.
Is the module PrestaShop 9 and multistore compatible?
Yes. Back-office controllers rely on ModuleAdminController for PrestaShop 8 and 9 compatibility, and the module handles the multistore context.