- 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
- Database Connection Setup
- Database Creation
- Database Restore
- Transfer Settings from Database
- Connecting a Second Computer
- 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
- 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
- Ace Hardware MAP & IMAP Pricing
- Ace Critical Retail Pricing
- True Value Price Levels
- True Value Store Assessment
- Importing from Excel
- Cost Break Analysis
- Cost Break Strategies
- Min/Max Strategies
- Strategy Backup & Restore
- Add Items from Catalog
- Store Grouping
On This Page
Paladin POS Import
What is this?
The Paladin import reads a text file exported from the Paladin POS system and loads it into Margin Master for pricing analysis.
Walk through it in the app: guide 4007 — Importing your Paladin data. Margin Master can walk you through these steps live: turn on Training / Guide Mode from the Help menu, then type 4007 into the Lessons & Guides box — or ask Margin Master support to run it with you.
Your Paladin export is a text file named MarginMaster*.txt with a header row, laid out as Margin Master support confirmed with you when your store was set up. It carries your item, store, department, pricing, cost, vendor, sales history and competitor price columns.
How Import Works
The export file is read from the Import Path set under Tools > Options > Miscellaneous:
- Place the Paladin export file (matching
MarginMaster*.txt) in the configured import directory. - Choose the import command on the Data menu. Margin Master reads the file, skipping its header row.
- The data is loaded into Margin Master's database.
- Your main pricing analysis tables are built from it.
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 MarginMaster*.txt |
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 | 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
The file name must start with "MarginMaster". Only files matching the pattern
MarginMaster*.txtare recognized during import. Rename your export file if needed.
Keep the header row. Paladin's export includes a header row, and Margin Master expects it. Export the file as Paladin produces it; do not remove the first line.
Numbers with thousand separators are fine. If your Paladin export formats sales figures with commas (for example,
1,234), Margin Master reads them correctly.
Paladin includes competitor pricing fields. Up to five competitor prices, a competitor price A, and a competitor memo can be imported for competitive analysis.
Common Questions
Q: What file name should I use?
A: The file must match the pattern MarginMaster*.txt. For example, MarginMaster_Export.txt or MarginMasterData.txt would both work.
Q: What if the same item appears twice for one store? A: Margin Master keeps one record per item and store, so a duplicate line in the export does not create a duplicate item.
Q: Are competitor prices required? A: No. Competitor price fields are optional. If your export does not include them, they will be empty in Margin Master.
