Margin Master Handbook
Introduction
Part I · Installing
- Prerequisites
- Firewall and Network Requirements
- Microsoft Edge Download Block
- SQL Server Authentication Setup for IT Administrators
- Antivirus and Endpoint Security Exclusions
- SQL Server Tools
- Install or Upgrade SQL Server Express
- Install or Upgrade SQL Server Management Studio
Part II · Introducing the Main Window
- A Tour of the Main Window
- The Menus
- The Button Row
- The Main Data Grid
- The Summary Section
- Banners and Badges
Part III · Initial Configuration
- The Options Window
- Store Configuration
- Miscellaneous
- Export Options
- Vendor Settings
- POS / Connections Tabs
- Background Service
- AI Assistant (Experimental)
- How POS Import Works
- Supported Point-of-Sale Systems
- Data Import Workflows
- RockSolid POS Import
- Epicor Eagle FTP Import
- Epicor MySQL Compass Import
- Transact POS Import
- Paladin POS Import
- Falcon POS Import
- Spruce POS Import
- Bistrack POS Import
- RockSolid Max POS Import
- ECS POS Import
- Prosperity POS Import
- Catalyst POS Import
- Westlake POS Import
- MI9 POS Import
- AS/400 POS Import
- CounterWorks POS Import
- Dimension POS Import
- PacSoft POS Import
- ProStix POS Import
- Sympac POS Import
- Propello POS Import
- EagleVision POS Import
- MySQL/Compass Connection Configuration
- ECI VPN Requirement (Spruce, RockSolid MAX)
- Propello POS Integration Guide
- MI9 Data Pipeline — Import to Main Table
- Troubleshooting: Epicor Import Brought In 0 SKUs
- PACE POS Import
- Advantage POS Import
- General Store POS Import
- J-3 POS Import
- KeyStroke POS Import
- AutBusSystem POS Import
- Tomax POS Import
- Enterprise POS Import
- Computakey POS Import
- Redisell POS Import
- DART POS Import
- MIB POS Import
- Substruct POS Import
- DMAS POS Import
- RODS POS Import
- Procom POS Import
- Agility POS Import
- Acumen POS Import
- Cruise POS Import
- LSandE POS Import
- Retalix POS Import
- DIBCorp POS Import
- GMROI POS Import
- ECi Advantage POS Import
- Sunray POS Import
- ActivantAutomotive POS Import
- IBS POS Import
- Versys POS Import
- RMS POS Import
- TAMS POS Import
- Integrasoft POS Import
- Dynamic POS Import
- Microsoft ARS POS Import
- CDS POS Import
- Spartan POS Import
- Nitterhouse POS Import
- Jeds POS Import
- Theisens POS Import
- Emery Jensen POS Import
- SMS Pro POS Import
- Burdens POS Import
- Intact POS Import
- Bloom Retail POS Import
- NCR Counterpoint POS Import
- Horizon POS Import
- Cloud Vendor Data Sync
- Data Aging and Freshness Warnings
- Resetting Vendor and POS Data
- Rebuild Data and Rebuild Selection Lists
- Troubleshooting Vendor Sync
Part IV · Customizing the Workspace
Part V · Basic Application Functionality
Part VI · Learning Margin Master
- Understanding the Strategy Hierarchy
- Pricing Strategies
- Creating a Strategy Step
- Updating and Deleting Steps
- Reviewing a Strategy and Running It
- Shared (Premade) Strategies
- SKU-Level Exceptions
- Manage Custom Groups
- Strategy Execution Cloud Tracking
Part VII · Advanced Topics
- Importing from Excel
- Cost Break Analysis
- Cost Break Strategies
- Min/Max Strategies
- Strategy Backup & Restore
- Add Items from Catalog
- Store Grouping
Part VIII · Updates, Troubleshooting & Help
- Data Diagnostics and Missing Index Recommendations
- System Diagnostics
- Margin Master Cannot Save Settings
- SQL Server 2025 Express vs. Full License
- Support Issue Management
- Catalog Lookup
- What's New After an Update
- Version History
- Documentation and the Help Buttons
Appendix
- CTLD — Do It Best Catalog File
- MARGIN_MASTER — Ace Catalog File
- PCDITEMXREF — Do It Best SKU Classification File
- SAP_ZONE_PRICE_MARGIN_MASTER — Ace Zone Pricing File
- PCDPRODCLASS — Do It Best Product Classification Hierarchy File
- SAP_STORE_DEPT_ZONE_MARGIN_MASTER — Ace Store Zone Assignment File
- Taxonomy — Ace Product Classification File
- Mapp_Pricing — Ace MAP & IMAP Pricing File
- margin_mstr_plano — Ace Planogram File
On This Page
AppendixUpdated 2026-03-24
PCDPRODCLASS — Do It Best Product Classification Hierarchy File
What is this file?
The PCDPRODCLASS file defines the Do It Best product classification hierarchy as a tree of nested XML elements. Each node has an ID, description, and classification type, with parent-child relationships expressed through XML nesting. Combined with the PCDITEMXREF file (which maps SKUs to classification nodes), this creates the taxonomy columns in the main table.
File Details
| Property | Value |
|---|---|
| File pattern | PCDPRODCLASS* (typically .xml) |
| Format | XML (hierarchical/nested) |
| Vendor | Do It Best |
| Frequency | As needed |
| Cloud table | DIBProductClassificationRecords |
Raw File Structure
<ProductClassifications>
<ProductClassification ID="100" ClassificationType="Dept" Description="Hardware">
<ProductClassification ID="200" ClassificationType="Class" Description="Fasteners">
<ProductClassification ID="300" ClassificationType="SubClass" Description="Bolts">
<ProductClassification ID="400" ClassificationType="FineLineClass" Description="Hex Bolts" />
</ProductClassification>
</ProductClassification>
</ProductClassification>
</ProductClassifications>
| XML Attribute | Data Type | Cloud Column | Description |
|---|---|---|---|
| @ID | string | ID | Unique classification node ID |
| @ClassificationType | string | ClassificationType | Node type (Dept, Class, SubClass, FineLineClass) |
| @Description | string | Description | Node description |
| (parent element's @ID) | string | ParentID | Reference to parent node; NULL for root nodes |
Cloud Table Mapping
| Source | Cloud Column | Notes |
|---|---|---|
| @ID | ID | Primary key |
| @ClassificationType | ClassificationType | e.g., Dept, Class, SubClass, FineLineClass |
| @Description | Description | Human-readable name |
| Parent element's @ID | ParentID | NULL for root-level (Dept) nodes |
Main Table Impact
This file indirectly populates the main table taxonomy columns. The DIB_Sku_4ClassificationLevel view walks the parent-child hierarchy to flatten each SKU's classification path into four levels:
| Main Table Column | Hierarchy Level | Description |
|---|---|---|
| DIB_Taxonomy1 | Level 1 (Dept) | Top-level department ID |
| DIB_Taxonomy1Desc | Level 1 (Dept) | Top-level department name |
| DIB_Taxonomy2 | Level 2 (Class) | Class ID |
| DIB_Taxonomy2Desc | Level 2 (Class) | Class name |
| DIB_Taxonomy3 | Level 3 (SubClass) | Sub-class ID |
| DIB_Taxonomy3Desc | Level 3 (SubClass) | Sub-class name |
| DIB_Taxonomy4 | Level 4 (FineLineClass) | Fine line class ID |
| DIB_Taxonomy4Desc | Level 4 (FineLineClass) | Fine line class name |
Business Rules
- Hierarchical traversal: Processing starts at root nodes where
ClassificationType="Dept", then recursively processes child elements, maintaining parent-child relationships. - Primary key: ID (unique across all classification levels).
- Companion file: PCDITEMXREF maps individual SKUs to leaf nodes in this hierarchy.
