Overview
This article explains how operators can connect their email accounts to MotionTools and automatically create packages from attached CSV files. If you want to use this feature, please reach out to our Customer Success Team.
Benefits
- Seamless Integration: Customers can stick to their existing process of sending CSV files to your operators email account, without needing to switch to a new channel (i.e. get used to the customer portal).
- Smooth Adoption: With customer import templates the structure can be mapped so that the customer nor the operator needs to adjust the csv file structure in order to get packages into your MotionTools account.
- Highly Customizable: The customer import templates allow heavily customizing the csv file structure and automatic import rules to fit the need of your business relationship.
- Automated Responses: The email importer can send automatic responses to your operations email or directly to the customer, minimizing the need for manual interaction.
- Easy to use: Admins can also send an email in behalf of the customer to the importer import@motiontools.com (or white labeled email) to trigger the email importer by mentioning the name of the customer in the subject they want to import packages for.
Prerequisites
- An active subscription with MotionTools.
- The feature must be enabled by the MotionTools customer success team.
- You do have Customers that can send CSV files (UTF-8 encoded) to your email.
Configuration Options
Defining the Import Template per Customer
General
- Valid Senders: Specify which emails are mapped as valid senders to the customer profile (e.g., example@test.de or all emails from @test.de).
- Response Emails: Decide whether the customer or the operator receives direct response emails.
- Header names: Define the mapping between csv headers and data in MotionTools.
- Values normalization: Define a list of values that will be accepted and then translated to proper package properties. I.e. for package size we accept: "palette", "palet", "pall" etc.
- Required Data: Specify required data fields such as destination address, delivery date, package properties, etc. so the sender receives an email response with clear indication what data is missing or not accepted.
- Automatic Rules: Set further rules for data processing.
Delivery Date/Time
- Delivery Date/Time: Determine if the date or datetime should be derived from the CSV, including format and timezone. It's also possible to derrive only the date and add a hardcoded time to it. Decide if this should be required, so we won't accept, if the datetime is in the past, or if not required we'd fallback to the next available time.
Destination
-
Mapping
- Full Address: This is the default option. The customer provides the full address details in the CSV.
- ID Mapping: Instead of an address a dedicated ID of the destination is provided which is mapped to a saved place. For this approach the sender just needs to share all destinations during onboarding and you'd need to create them with the external_id attached as saved place.
- Timeslots: Check if a timeslot is collected for the given destination.
- Save to master data: Decide if during the import we save destinations as saved places & with it the given timeslot, if not yet given.
Pickup
-
Mapping
- Pickup Address: The full pickup address is provided in the CSV.
- ID Mapping: Instead of an address a dedicated ID of the pickup place is provided which is mapped to a saved place.
- Hardcoded: We define a hardcoded id of a pickup place which we always use for the import.
- Hub Selection: The hub is choosen based on the destination’s service area or zone if the customer drops off the package at the operator’s hub.
Additional Fields
- Package Weight: Specify the unit (grams / kilograms / tonne).
- Package Quantity: Indicate how many packages to create of this kind.
- External Labels: Include labels for scanning.
- Metadata: Attach external IDs to the package.
