Deliveries
Project
|
Role
|
The problem is that a cafe manager can not accurately update invoices on items that they received. What they think they are getting, isn’t actually what they receive. As well as what we ordered for them and think they are getting, is not always what they get. We needed to create a system that keeps invoicing digital instead of manual.
The current process was to order for a cafe, send them an email the morning of, telling them what they are receiving for the day. Then in the morning the delivery is out front with a paper receipt of what was delivered. The cafe would then open up the delivery and contact the vendor for any refunds needed. So that's our company ordering, the vendor is delivering, cafe is receiving, then it becomes unclear where the error was.
We decided to take away this need for the cafe to get involved with the vendor, instead we took over contacting the vendor for discrepancies. But how could we receive this information from the cafe manager? He can’t reply to each daily email manifest with his corrections, that would be too tedious and error-prone. We decided to take this read-only email format, and make it dynamic.
The current process was to order for a cafe, send them an email the morning of, telling them what they are receiving for the day. Then in the morning the delivery is out front with a paper receipt of what was delivered. The cafe would then open up the delivery and contact the vendor for any refunds needed. So that's our company ordering, the vendor is delivering, cafe is receiving, then it becomes unclear where the error was.
We decided to take away this need for the cafe to get involved with the vendor, instead we took over contacting the vendor for discrepancies. But how could we receive this information from the cafe manager? He can’t reply to each daily email manifest with his corrections, that would be too tedious and error-prone. We decided to take this read-only email format, and make it dynamic.
Preliminary wireframe exercise of a rejected layout flow.
We added a new section to our pre-existing in-store app called My Deliveries. This is where the user can see what deliveries to expect and have a chance to correct discrepancies on the go. Above left image is an early rejected flow, where you enter edit mode for the list of numbers to turn into inputs.
We validated our hypothesis' by user researching and usability testing. I developed multiple prototype rounds to review/test with both current cafe stakeholders and random local cafe managers. Below is our MVP solution's planned work divided out by sprint velocity.
We validated our hypothesis' by user researching and usability testing. I developed multiple prototype rounds to review/test with both current cafe stakeholders and random local cafe managers. Below is our MVP solution's planned work divided out by sprint velocity.
Above is the MVP solution's planned work divided out by sprint velocity.
Final screens and an iPad view.
|
|
As a result, we implemented a calendar view of orders per vendor in a list of what is expected. You can click on any item to update the amount you received, select a reason for what happened, leave a further detailed note, and attach a photo. We integrate this data directly into our system, which corrects current inventory counts and adjusts orders in the background. We also have a digital trail of invoices now and can follow up with the vendor for problems with clear data points. At the start of the day, our platform easily stores more accurate data about the number of croissants a cafe actually has on hand!
