Skip to content

Customer Implementation Requirements Guide

OrderFlow Ltd.

Document Version: 4.2.4

Document Built: 2024-02-16

This document and its content is copyright of OrderFlow Ltd. All rights reserved.
You may not, except with our express written permission, distribute, publish or commercially exploit the content.
Any reproduction of part or all of the contents in any form is prohibited.

Site, Channel and Organisation Scope

Site, Channel and Organisation Scope

Many OrderFlow functions can be scoped to specific sites, channels or organisations, meaning that OrderFlow can be configured to behave differently depending on the site, channel or organisation it is working with.

A site represents a specific warehouse, which may be an actual building, or section of a building, where certain order types are processed. An example of site-scoped behaviour is that OrderFlow can print different returns addresses on the despatch note.

A channel represents a specific eCommerce system (for example, Magento) that sends orders to OrderFlow. An example of channel-scoped behaviour is that OrderFlow can handle all orders that are imported from a specific channel as a priority, or select a special courier service for orders placed on that channel.

An organisation represents a company, which can have one or more channels. An example of organisation-scoped behaviour is that OrderFlow can use different logon credentials when getting a label from a Courier system.

Typically, for a retailer, there will be one organisation associated with multiple channels on OrderFlow. As a minimum, there must be at least one site, organisation and channel configured. For a 3PL, initially we may set up a test organisation and channel, which will be activated as soon as they are ready for Go-Live.

  • How many sites, organisations and channels do you need to be configured on OrderFlow?
  • What are their names?
  • What is the address of each site?