I’m wondering if/how many folks out there would like to have a feature that allows staff to enter and maybe even adjust the sales date for an order. We can’t always process an order on the same day we take an order. This makes trying to analyze historical sales data frustrating.
I don’t think Vin 65 would need to do much. They could simply add a text field somewhere that makes sense when an order is being rung in that could then be utilized in reports. Essentially each order could have a “Processing Date” and a “Sales Date”
I’ve made the suggestion to Vin 65 and they might be working on it, but I wanted to see if I could gather support in order to increase the odds of it happening.
I wouldn’t be overly optimistic that they are in fact working on it.
I think it’s a good idea. I wonder if it would have any ramifications for any existing reports or third-party integrations, however, which might make it a huge project.
We already use Vin65 in this fashion if I’m understanding what you are wanting to do.
submitted date is when the order is placed.
completed date is when the order is completed/processed.
These dates are not the same in our system. When an order is placed it is in Paid/submitted status. When it’s picked up or shipped the order then becomes completed.
i’m actually surprised more wineries don’t use this setup in Vin65.
What I would need is to be able to edit one of those dates, either while processing the order or after its been been submitted/completed.
Maybe an example of a situation would help to explain what I’m looking for. Say an employee takes an order on Friday and the customer writes their info on an order form. Then that employee gets too busy selling wine for the rest of the day and they can’t get to processing the order until the following Monday. Now that order rings in as being processed on that Monday, not Friday when the order was actually placed. Assuming that happens many times over, Mondays start to look like the busiest day of the week, when in fact its not.
Does that help to clarify the solution I’m looking for? Thanks for your thoughts on the topic!
The existing reports would have to be updated, and that’s the point. I need to have this information in a report in order to better analyse sales data. My thought would be something very similar to the “Source Code” that exists in the Admin Panel (I’m not super familiar with POS). Just a text field where a date could be entered and then also show up on a report.
The third party integration is not something I can comment on much or have thought to much about. But I imagine they can create the feature in a way so that the info/feature does not get passed onto any third parties.
This also seems like a basic enough of an issue that it if it is a big fix it would be worth it. But maybe that’s just me and that’s sort of the reason for this thread, to see if and how many others could utilize a feature like this.
That’s a totally realistic, practical use-case. But Vin65 might respond suggesting you alter your workflow and enter in orders while the customer is there or during your closing procedures that day. If there is an order form with card information floating around over several days, it might also threaten your PCI compliance.
Would you just want this date reflective in reports, or would you want it to be the canonical date of sales throughout Vin65? Like, if you wanted to search orders by date in the Admin Panel, would it be searching for your custom date or the date it was transacted in Vin65?
I think you and I would agree that adjusting a business in order to accommodate software is not the way this should work for a variety of reasons. We do have systems in place to keep our customers info safe and secure.
All I need is for the data to to be reflected in the reports. Anything beyond that would probably prove to be useful, but not necessary to my purposes.
I certainly don’t disagree with you, but knowing how Vin65 operates, they build software to comply with best practices and rarely will develop for anomalous workflows, especially if it conflicts with best practices.
