Our primary lead source comes from Canada Post neighborhood mailings. Right now we are sending about 300K flyers/month across 4 divisions but will be increasing to 450K plus come the new year. We have over 20 areas a week and multiple flyer types which we are looking for a more stable way to keep track of.
I am wondering a couple of key things before I dive more heavily into mastering this myself.
-
As we schedule new routes, is a recurring date scheduling function something that can be coded in? From what I have come across, this is not something I’ve seen others need to use, but for us it would be essential. Ideally as a mailing route is generated you could schedule it one of 3 ways.
a: Say the route has 10,000 homes, and you want to send them out over 4 weeks on mondays starting X date, it splits up the routes (taking into account the varying number of homes) and generates a plan with an assigned flyer type.
b: You want to send at least 2000 flyer per week starting on X date and the number of weeks are generated
c: you are able to slot in data at will from the weekly view to fill in holes -
As I mentioned we utilize a tool provided by Canada Post. Are we able to program our Airtable in such a way where it communicates with Canada Post, generates the necessary paperwork, and saves the data. You can export .csv from this tool. Ideally we are looking for it to function by inputting the route data so we can schedule it, and then at a later date recalling a portion of that data, using it to complete a form which generates a PDF of the paperwork. Sometimes the data varies on the date we prepare the paperwork from the date it was initially planned, this number would need to be recorded as well. Are we able to have this tool function in Airtable without needing to go to an external site?
-
Are we able to incorporate a map view? Ideally generating postal codes. We would love to be able to plot the data and know how many times we’ve mailed a certain area without combing through data.
-
I would also be adding in invoicing, inventory, and CRM data but this is much less complicated then the above queries.
-
How complex of a project would this be? I have begun to create a layout and wrap my head around how we want this to function and look, so there will be a jump off point as well as a ton of data.
Any hits, tips, tricks are valued!


