Account and Retailer Design - Fluent OMS Discovery
Essential knowledge
Changed on:
22 Oct 2024
Overview
Determine a suitable design of the Fluent Account and Retailer Structure for based on client requirements and Fluent recommended practice.This is usually the first key design decision that all other project decisions flow from, and cannot easily be changed once taken, so is an important topic.Understand the key considerations for designing the correct structure (including future requirements which may influence design) and some common account design patterns including the pros and cons for each approach.Key points
- Fluent data model and the importance of account design
- Common decision points that need to be considered when deciding the best approach
- Examples of common account designs and the pros and cons for each- (e.g. retailer per brand/country, vs grouped retailers per region, brand, etc.)
- How to future proof the approach
Key Terms
- Account: Represents a single tenant within the Fluent platform and is the root of the hierarchy.
- Retailer: A logical division within an Account (e.g. brand, country, etc.)
- Network: A logical grouping of Locations.
So, what’s the role of an Order Management System?
- Connects all applications associated with inventory, locations and customer orders.
- Acts as the system of record for stock availability across the entire supply chain.
- Orchestrates orders across the enterprise to ensure optimal fulfilment.
Connect your Sales and Distribution Channels
