Margin Master Handbook
- 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
- A Tour of the Main Window
- The Menus
- The Button Row
- The Main Data Grid
- The Summary Section
- Banners and Badges
- 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
- 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
- Importing from Excel
- Cost Break Analysis
- Cost Break Strategies
- Min/Max Strategies
- Strategy Backup & Restore
- Add Items from Catalog
- Store Grouping
- 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
- 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
PacSoft POS Import
What is this?
PacSoft is a point-of-sale system for retail operations. Margin Master imports PacSoft CSV exports to build pricing analysis tables.
Import File Format
| Property | Value |
|---|---|
| Delimiter | Comma (,) |
| File pattern | *.csv |
| Header row | Yes (1 row) |
| Total fields | 22 (strict validation) |
PacSoft enforces strict field validation. Each row must contain exactly 22 fields or it will be skipped during import.
How Import Works

The export file is read from the Import Path set under Tools > Options > Miscellaneous:

- Export your data from PacSoft as a
.csvfile. - Place the file in the configured import folder.
- Margin Master reads the file and validates each row. Rows that do not contain exactly 22 fields are skipped.
- Valid data is staged using BCP (Bulk Copy Program).
- The staged data is finalized and inserted into the
[Store]table. - Margin Master joins the store data with vendor catalog data to build your main pricing analysis table.
Field Mapping
| PacSoft Field | Margin Master Field | Notes |
|---|---|---|
| Sku | SKU | Product identifier |
| Store | Store | Store identifier |
| Department | Dept | Department code |
| Class | Class | Product class |
| Description | Description | Product description |
| CurrentPrice | CurrentPrice | Current retail price |
| Cost | Cost | Product cost |
| OnHand | OnHand | Inventory quantity |
| Location | Location | Bin/shelf location |
| H0 | History0 | Current period sales |
| H1–H12 | History1–History12 | Monthly sales history |
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| No Files Found when you choose Get POS Data | The export is not in the Import Path (Tools > Options > Miscellaneous), or its name does not match the pattern above | Check the path and the file name; Margin Master reads only the current folder, not sub-folders |
| The same file is imported again and again | The previous import's file was not renamed | After a successful import the file is renamed to NAME[ext].BAK; a file that keeps its name did not import - read the error dialog |
| 0 records or far fewer than expected | The export covers the wrong store, or the store is not matched in the Store Manager | Open Store Manager and check the store's row; re-export from the point of sale |
| Columns land in the wrong fields | The export layout changed | Compare the file's header row with Field Mapping above; contact Margin Master support with the file |
| Import finishes but the grid does not change | The rebuild was postponed (the Click to update data badge is showing) | Click the badge, or Data > Rebuild Data |
Every import failure shows one error dialog; the log under File > Utilities > Show Log Files has the detail to send to support.
Tips
- Strict 22-field validation: Every row in your PacSoft export must have exactly 22 fields. If a row has more or fewer fields (perhaps due to commas in description text or missing columns), that row will be skipped. Check your export settings if you see records being dropped.
- Clean field set: PacSoft has a straightforward mapping with standard fields. No special conversion or transformation is applied beyond the field count validation.
Common Questions
Q: Some of my records are missing after import. What happened? A: PacSoft enforces a strict 22-field-per-row requirement. Rows with a different number of fields are silently skipped. Common causes include commas embedded in description fields or missing trailing fields. Review your CSV export to ensure each row has exactly 22 comma-separated values.
Q: Can I change the expected field count? A: No. The 22-field requirement is built into the PacSoft import mapping and cannot be configured.
