Business unit data
Business Unit Specific Data
When integrating with Hii Retail, it's important to understand how you manage and distribute your master data.
Hii Retail allows you to assign master data in two ways: at the Business Unit Group level or, as described here, at the Business Unit-specific level.
Overview
Retailers often organize stores (Business Units) into groups or hierarchies based on size, location, or other characteristics. For example, city-center stores may have different pricing or assortment than rural stores, or some stores may have in-house cafés or on-site production.
These differences may require treating certain groups of stores differently.
This section focuses on scenarios where grouping is managed within your ERP system, and Hii Retail receives fully prepared, Business Unit-specific data.
When to Use Business Unit-Specific Endpoints
Use these endpoints when your ERP or PIM generates data for each Business Unit in your organization.
Integration Requirements
When integrating at the Business Unit-specific level, your ERP system must handle all necessary data processing. Data sent to Hii Retail should be complete and ready for downstream distribution.
Requirements:
- All data in POST or PUT requests must be complete.
- The Business Unit ID must exist downstream; Hii Retail does not validate this before distribution.
- PATCH or DELETE requests have no effect if the specified data does not exist.
- PATCH requests update individual properties of existing data.
- If a Business Unit Group ID is provided to these endpoints, no actions are taken and no outputs are generated.
API Documentation Links
- Business Unit-Specific Endpoints for Items
- Business Unit-Specific Endpoints for Price Specifications
- Business Unit-Specific Endpoints for Additional Item IDs
- Business Unit-Specific Endpoints for Item Links
- Business Unit-Specific Endpoints for Promotions
- Business Unit-Specific Endpoints for Content Declarations