Back

How to prepare your data to be uploaded

Before uploading your site data into Sloc Local, here’s everything you need to know to get your file ready. Following these guidelines helps your upload run smoothly and sets your project up for accurate local merger analysis.

File requirements
  • Accepted file types: .csv or .xlsx. If you have an older .xls file, open it in Excel and save it as .xlsx first.

  • Maximum file size: 5MB

  • Maximum number of rows: depends on your plan. The limit is shown on the upload screen as Max rows.

  • Put the table on the first sheet - Sloc only reads the first sheet of an Excel file

  • The table should start in the top-left cell (A1)

  • Include column headers in the first row

  • CSV files should be comma-separated, ideally saved as UTF-8

✅ Do’s
  • Table starts in cell A1

  • Column headers in row 1

  • Just one sheet in the file

  • No other tables, titles or comments

A spreadsheet laid out correctly: one table starting in cell A1 with headers in row 1
🚫 Don’ts
  • Multiple sheets

  • Extra tables included

  • Table doesn't start in cell A1

  • Table titles and comments throughout

A spreadsheet laid out incorrectly, with titles, comments and extra tables
Table format
  • Each row should represent one site (highlighted in red)

  • Each column should represent a field of information about that site (store name field highlighted in blue)

A site table where each row is one site and each column is one field
Fields to include

When you import, Sloc asks you to match your columns to its fields on the Map fields screen. Two are required.

Site name (Required)

Used to identify each site throughout the workflow.

  • Should be clear and easy to understand

  • Ideally unique to avoid confusion

💡 If some site names repeat, Sloc can make them unique for you during import.

Fascia (Required)

The brand or owner each site belongs to. Sloc uses it to group sites under common ownership when modelling mergers.

  • Ideally aligned with your internal fascia classifications

  • Should be consistently typed across rows

💡 Don’t worry if names vary, for example "Co-op" and "The Co-operative Group". You can review and tidy fascia names while you import.

Location (Optional)

Precise location data is essential for local merger analysis, but sites without coordinates can be located after import.

Best case: You already have latitude and longitude in separate columns.

Latitude and longitude in two separate spreadsheet columns

If coordinates aren’t available, Sloc Local can batch geocode your sites from their address information, so include any address information you have.

This address information might take the form of:

  • A full address column. Sloc Local can geocode from a single full address field.

    A single column holding each site's full address



  • Separate address fields (e.g. street, town, postcode) allow more robust and flexible geocoding - including geocoding by exact postcode match.

    Address details split into separate street, town and postcode columns

It is always best to include any address information you have - and to split address fields where possible.

Additional information (Optional)

You may also include other site-level data such as:

  • Site size

  • Revenue

  • Store type

These fields are useful for filtering and reviewing your sites, for building subsets, and for weighting sites in your analysis (for example by revenue or store size).

💡Pro tips
  • Use clear column names - this helps Sloc Local detect fields automatically

  • Ensure numeric fields (like latitude/longitude) don’t include non-numeric characters

  • No need to perfect your data - Sloc Local has built-in tools for cleaning and formatting

  • That said, tidying your data beforehand can help reduce upload size and improve performance