How to import a delivery spreadsheet and turn orders into stops

When orders arrive in a spreadsheet, copying addresses one by one into a route planner takes time and creates room for mistakes. Genne's spreadsheet import shortens the process: upload the file, review a preview organized by row and turn valid records into stops on a new route.

The benefit is not just less typing. A good import preserves operational information, helps identify inconsistencies before routing and leaves the sequence ready for review.

What to include in the spreadsheet

Use the first row to name columns clearly. As a starting point, include:

• address;
• additional address details, where applicable;
• order identifier;
• useful delivery notes.

The address should be complete enough to distinguish the destination. IBGE explains that an address can include street, number, additional details, locality, CEP, municipality and state. The more ambiguous the text, the more likely the location will need correction.

Google also recommends complete, unambiguous postal addresses for automated geocoding. In practice, prefer “Rua Exemplo, 120, Centro, Campinas - SP, 13000-000” over vague records such as “Rua Exemplo, Campinas”.

Do not mix delivery instructions into the address field. “Leave at reception” or “call on arrival” works better as a note. Additional details should identify the unit — for example, “block B, apartment 42” — without replacing essential address components.

How importing works in Genne

In the planner, start the import flow and select the spreadsheet. Genne generates a preview of records before adding them to the route. This step lets you check how each row was interpreted, review addresses and keep the identifier and notes associated with the order.

If several rows represent orders at the same destination, they can be combined in one stop. This avoids creating repeated points for a single address and keeps orders identified within the corresponding visit.

The preview is the best time to correct data. Check especially:

1. whether the address matches the expected destination;
2. whether additional details are in the correct field;
3. whether the order identifier was preserved;
4. whether the note helps the driver without cluttering the address;
5. whether different rows really represent different destinations.

After confirmation, stops enter the plan and can be reviewed before the route is calculated.

A simple organization model

A lean structure can follow this pattern:

In this example, orders PED-1001 and PED-1003 point to the same destination and can be treated as one stop with two items. The identifier remains important so that operational completion does not depend solely on the street name.

Exact column names can vary by file and available workflow, but clear headers make review safer. Google My Maps help follows the same principle: tabular files should have headings in the first row and a column that can locate each record, such as an address, place name or coordinates.

Common mistakes that delay the route

Incomplete address

A street without a number, city without a state or destination without a CEP can point to more than one place. Complete what is available and confirm the location in the preview.

Additional details inside the street field

Apartment, block, room and internal references should be kept separate whenever possible. This improves readability and prevents unit details from interfering with the main address search.

One row per package without an identifier

Multiple packages may belong to the same order or stop. Without a consistent identifier, checking becomes harder. Use a unique order code and put quantity or additional details in their own fields.

Generic notes

Notes such as “urgent” tell the driver little. Prefer actionable instructions: “reception via Rua B”, “customer receives after 14:00” or “intercom 42”.

Unreviewed duplicates

Two identical rows may represent two legitimate orders at the same address — or an accidental duplicate. The preview helps distinguish these cases before they reach the map.

Checklist before confirming

Before completing the import, review quickly:

• all records have an identifier;
• street, number, city and state abbreviation are present;
• CEP is provided when available;
• additional details are separate from the main address;
• notes contain only operational instructions;
• orders at the same destination were recognized correctly;
• no duplicate row was added by mistake.

From spreadsheet to street

Importing the spreadsheet is the beginning of planning, not the end. After confirming the stops, check the starting point, adjust priorities or necessary details and then calculate the route. If a destination looks incorrect, return to the address and correct it before starting navigation.

This workflow concentrates preparation in three moments: organize the spreadsheet, validate the preview and review the route. The team reduces manual work without giving up the checking that makes a difference in execution.

Sources

• Google My Maps: import map features from a file
• Google Maps Platform: best practices for address geocoding
• IBGE: Addresses
• IBGE: Address Registration Standard