LogoLogo
CommunitySupport PortalYouTubeStart a free trial
  • Welcome
  • Commerce Engine
  • Orchestration Engine
  • API Documentation
  • Release Notes
  • Changelog
  • Commerce Engine
  • Getting Started
    • General Concepts of Emporix
    • Creating your first tenant
    • Developer Portal
      • Manage Users
      • Manage API Keys
      • Tenant List
      • My Account
      • Manage Showcase and Sample Data
  • Customer Use Cases
    • Commerce Use Cases
      • Quote Process
      • Orders
      • Coupons and Redeeming Rewards
      • Returns
      • Payments
      • User Management and Approvals
      • Customer Social Login
      • Personalized Commerce - Customer Segments
      • Company Shared Orders and Customer Groups
    • Automated Use Cases
      • First Registration Coupon
      • Availability and Warehouse Assignment
      • Quote and Order Entry Automation
  • System Management
    • Introduction
    • Authentication and Authorization
      • Identity and Access Management (IAM)
      • Auth0
      • Emporix Single Sign-On (SSO)
    • Webhook Event Publishing
      • HTTP Webhook Strategy - HMAC Configuration
      • HTTP Webhook Strategy - Integration with Azure Service Bus
      • HTTP Webhook Strategy - Integration with Amazon Simple Queue Service (SQS)
    • Search
      • Universal Search Connector
      • Search Configuration
      • Indexing Service
    • Optimistic Locking
  • Extensibility and Integrations
    • Extensibility Cases
      • External Products, Pricing and Fees
      • Enabling Custom Extensions
    • Integrations
      • SAP Integration
    • Payment Systems
      • PayPal
      • Saferpay
      • Spreedly Gateway
      • Unzer
    • Third Party Add-Ons
      • Emporix Contentful App
      • Emporix Builder.io Plugin
      • Magnolia Emporix Connector
      • Zendesk Emporix Connect
    • Powered by AI
      • AI Smart Config
      • AI Smart Import
  • Core Commerce
    • Introduction
    • AI Assistance
    • Carts
    • Catalogs
    • Categories
    • Coupons
    • Customer Management
      • Approvals
      • Assisted Buying
      • Customer Groups
      • Customer Segments
    • Data Localization
    • Delivery Cycle Management
    • Mixin Schemas
    • Media Management
    • Orders
      • Shared Orders
    • Pricing
      • Pricing (Legacy)
    • Products
      • Availability, location, and stock levels
      • Brands
      • Labels
    • Quotes
    • Returns
    • Reward Points Management
    • Sites
    • Tax Classes
      • Tax classes (Legacy)
    • Measurement Units
  • Management Dashboard
    • Introduction
    • Customer Management
      • Companies
      • Customers
      • Groups
      • Segments
      • Coupons
    • Quotes
      • Quotes
      • Status Codes
    • Orders
      • Orders
      • SEPA
      • Returns
    • Catalogs
      • Catalogs
      • Categories
    • Products
      • Products
      • Product Templates
      • Labels
      • Suppliers
      • Brands
      • AI for a Product Description
    • Pricing
      • Price Models
      • Price Lists
    • Settings
      • Sites
      • Shipping Zones and Methods
      • Delivery Times
      • Units
      • Tax
      • Countries
      • Currencies
      • Languages
      • System Preferences
      • Custom Entities
      • Mixin Schemas
    • Administration
      • Users and Groups
      • Extensions
      • API Statistics
      • Webhooks
    • Extensions
    • Custom Instances
  • Additional Resources
    • Glossary
    • Videos
    • Emporix Community
Powered by GitBook
LogoLogo

Resources

  • Emporix.com
  • Developer Policy
  • Terms of Use

Find us

  • LinkedIn

© 2025 Emporix. All Rights Reserved.

On this page
  • Purpose
  • User groups
  • B2B Admin
  • B2B Buyer
  • B2B Requester
  • Working with approvals

Was this helpful?

Export as PDF
  1. Core Commerce
  2. Customer Management

Approvals

In B2B segment, having an appropriate approval process in place is crucial.

PreviousCustomer ManagementNextAssisted Buying

Last updated 1 month ago

Was this helpful?

Here you can find an overview of the Emporix Approval Service, along with its features and benefits. The approval process is relevant only for the B2B customers.

  • Looking for Management Dashboard guides? Check out the System Preferences and Customers guides.

  • Looking for related API documentation? Check out the API.

Purpose

An approval process is necessary for the organization to define the correct purchasing flow and budget limits. Depending on the role of the customer who creates an order, some orders are approved automatically, while others require additional confirmation from eligible users.

The approval flow starts when a customer uses the storefront to add products to the cart.

User groups

To improve management of the approval process, the following roles are introduced:

  • Customer Administrator - B2B_ADMIN

  • Purchaser of the Customer - B2B_BUYER

  • Material Manager - B2B_REQUESTER

B2B Admin

When the customer is assigned to the admin B2B_ADMIN group, the checkout triggers in a standard way. There is no additional step to create an order.

B2B Buyer

When the customer is assigned to the admin B2B_BUYER group, the approval service checks if the customer has permission to trigger the checkout.

  • If the cart price is within the company limit, the customer can finish the order themself.

  • If the cart price exceeds the company limit, the customer creates the approval for the customer approver - the approvers list can be fetched from the approval service. When the approval is created, the approver can finish the checkout process and create the order.

B2B Requester

B2B requester is a material manager. When the customer is assigned to the admin B2B_REQUESTER group, the approval service checks if the customer has permission to trigger the checkout. The requester customer cannot trigger the checkout, so the approval needs to be created.

  • If the cart price exceeds the company limit, the customer can only assign a customer approver, who belongs to the B2B_ADMIN group.

  • If the cart price is within the company limit, the customer can only assign a customer approver, who belongs to the B2B_ADMIN or B2B_BUYER groups.

The approvers list can be fetched from the approval service.

Working with approvals

When the approval is created in the storefront, the approving customer receives an email with a notification that the approval request was created. If any additional comments were provided by the requester, they are also sent to the approver.

After a customer creates an approval, the following data is automatically populated:

  • Requester - the value is populated based on a customer token.

  • Approver - firstName and lastName values are populated based on the customer ID.

  • Resource - refers to an order, the value is populated based on cart data.

  • Expiry date - by default the expiry date is set to +10 days from the day when the approval was created.

  • Approval status - the status is set to PENDING by default.

Within the existing approval, the following scenarios are possible:

  • A requester can update data from the approval: comments, details, delivery windows, statuses. The update is possible only when the approval status is PENDING.

  • A requester can change status to CLOSED.

  • An approver can change status to the APPROVED or DECLINED.

  • After expiry date, the approval status is changed automatically to EXPIRED.

Approval Service