Digitizing Shipping Documents with Google Docs

(Kendrick Lu) #1

AppSheet Workflows can be used to automatically send notifications, change data, or generate documents. Below is an example of Workflows in action.

If you’re in the shipping industry, your company probably has a lot of papers and forms flying around. Aside from being costly and wasteful, it can also be difficult to keep track of all these different documents.

So, we’ve created three commonly-used form templates that you can use to digitize these processes: a Shipping Invoice, a Delivery Receipt, and a Bill of Lading. With these sample apps and shared templates, you can quickly generate PDFs of these forms.

Each of these templates is part of a sample app; just input your information into the app, and a workflow will send the filled-out template to the email that you provide.

View or copy any of these Apps & Templates here to generate your own Invoices, BOLs, and Receipts:

Shipping Invoice App

Bill of Lading:

Delivery Receipt:

Hope you guys find this useful! If you’ve got any questions, comments, or feedback, drop it in the comments below :point_down:

(Kendrick Lu) #2

If you’d like to create your own digitized template for another purpose, you’ll need to install the Google Docs AppSheet add-on.

1 Like

@kendricklu - thanks for sharing! Side question - how do you approach the choice of a standalone app for each function, vs combined apps with more than one function (eg: shipping + receiving). I find it more difficult to keep look, feel, and behavior the same across separate apps (eg: format rules, action layout, slices, etc). Was wondering where you think the balance is…

As soon as you split, you have three times the complexity - but reduced performance issues. Thoughts?


I think for demo purposes it is probably easier to have standalone apps.


@Lynn - my question was more about apps in use (not demos).

1 Like
(Kendrick Lu) #6

Hey Mike, great question. This is definitely an issue that I had to consider when creating these three apps. I think what pulled me to go with three separate apps was the question of who my end user was - namely, the AppSheet community. I felt that it would be easier for community members to digest and experiment with if each app performed just one function, rather than lumping it all together into one app.

Supposing I was creating an app (or apps) for someone super familiar with AppSheet, I’d probably consolidate them. Again, I’m leaning towards the thought of user satisfaction in this answer, but I wouldn’t want want my users constantly bouncing between a shipping app and a receiving app, for example. That’s personal preference, but user experience is certainly a huge factor that should be considered when approaching this question, and designing any app.

Hope this helps!


Certainly makes sense for the demo, and a great way to help users learn.

I was actually just thinking about the end user switching apps as you noted below (and not thinking demo only).

Thanks for sharing these great examples!