Epicor Eagle FTP Import

What is this?

The Epicor Eagle FTP import downloads your inventory file from your Epicor Eagle server via FTP or SFTP and loads it into Margin Master for pricing analysis. This is the standard import method for Epicor Eagle stores that pair with Ace Hardware or Emery Jensen vendor data.

There is no file for you to export or place: Margin Master connects to the Eagle server with the credentials you enter in Options and downloads the file itself.

How Import Works

1. Connect via MySQL / Compass - leave unchecked for the direct Epicor FTP connection.
2. IP Address, Port, Username, Password and Use Secure FTP - the Eagle server credentials.
3. Test & Save Connection / Troubleshoot Connection...
4. Restore from Cloud... - pull the connection saved for this store.
5. Import Options - Batch Import Files (BCP) and Streaming Import.
6. Open Store Manager... - POS-to-vendor store mapping.
7. Store Number Display & Sorting.

When you choose Import Data:

1. Margin Master connects to your Epicor Eagle server using the FTP or SFTP credentials configured in Options.
2. It downloads the current inventory file from the server.
3. The Eagle store letters in the file are matched to your store numbers.
4. The inventory data is loaded into Margin Master and your per-store main tables are built from it together with your Ace or Emery Jensen catalog.
5. Ace Direct SKUs, MAP pricing and zone pricing are applied to the finished tables.

Re-Importing a Previously Downloaded File

Margin Master keeps a copy of the last file it imported successfully on this computer. If the Eagle server is offline or unreachable, or you need to reprocess the last download while troubleshooting, ask Margin Master support to re-run the previous download. Support can re-import that copy without connecting to the Eagle server at all.

Clicking Import Data normally downloads a fresh file. If the Eagle server is unavailable at that moment, you will see an error message; nothing already imported is changed.

Troubleshooting

Every import failure shows one error dialog; the log under File > Utilities > Show Log Files has the detail to send to support.

Main Table Processing Mode

The Epicor tab under Tools > Options > POS / Connections has one setting, Use a single main table (one row per SKU per store). It chooses how the main tables are laid out; it does not change what the strategies do or the prices they produce. It is offered on both Epicor import routes, this FTP import and the MySQL/Compass import.

• Off (the default) - multi table processing. Margin Master builds one main table per store. Selecting a store picks that store's table.
• On - single main table processing. Margin Master builds one table with one row per SKU per store. Selecting a store filters that table by store number instead of choosing a table.

Changing the setting does nothing until you close the Options window. You are then asked to confirm, and the confirmation names every main table that will be replaced. If you answer Yes, Margin Master builds the new table first and removes the old ones only once the build has succeeded, so a failed rebuild leaves everything as it was. No keeps the current mode; Cancel returns to Options.

Either way the rebuild reads the Epicor data already on this computer (it does not download the file again), builds each store's rows exactly as that store's own table is built, applies the vendor catalog, zone pricing and MAP pricing store by store afterwards as the multi table build does, and discards all current pricing work - future prices, applied rules and locks. Re-run your strategies afterwards. Later imports rebuild the single table in the same way. Rows the export files under the store * (Epicor's all-stores marker, typically coupons) are left out of the single table; multi table processing does not use them either.

Store grouping on the FTP import keeps multi table processing for now. With Use Store Grouping? on (Store Information tab), the single main table cannot be selected on this import route; turn store grouping off first, or keep multi table processing. The Compass import supports both.

Tips

Store letters map to store numbers. Epicor Eagle identifies stores by single letters (A, B, C and so on). Margin Master matches them to your numeric store numbers from your store configuration.

FTP credentials are configured in Options. Go to Options, then the Epicor tab (with Connect via MySQL / Compass unchecked) to set your Epicor Eagle FTP server address, username, and password. Both standard FTP and SFTP are supported.

Ace Direct SKUs are handled automatically. Items with SKU numbers ending in "D" (Ace Direct items) match their Ace catalog records without any change on your side.

Zone pricing is applied after import. If your store has zone-specific pricing configured, Margin Master applies the zone prices from your synced Ace zone data once the main tables are built.

Common Questions

Q: What vendor data does Epicor Eagle use? A: Epicor Eagle pairs with Ace Hardware or Emery Jensen vendor data. Your Ace/EJ catalog must be synced from the cloud before building main tables.

Q: What is the difference between FTP and MySQL Compass import for Epicor? A: FTP import downloads the inventory file directly from the Eagle server. MySQL Compass reads from a local Compass data warehouse on your network. Both produce the same result. Use whichever method your store has configured.

Q: Why do I see letters instead of store numbers in Epicor? A: Epicor Eagle uses single letters (A-Z) as store identifiers. Margin Master translates them to your numeric store numbers automatically.

Q: What are the two import modes? A: Direct mode is the standard mode and is what you should normally use. BCP mode is a troubleshooting option; use it only when Margin Master support asks you to.

Q: What is MAP pricing? A: MAP (Minimum Advertised Price) enforcement ensures that future prices do not go below manufacturer-set minimums. This is applied automatically after import for Ace Hardware items.