Skip to main content

How to Manually Send Data

Updated

Sending Data Manually from On-Premise Systems

If you have just installed and want to send back data for your reporting needs, follow the instructions below. Some systems have a limit on how far back data can still be extracted, so please check your POS Guide for your system before attempting to manually send back data. 

These instructions can also be used to resend data if a daily send was missed for any reason. 

Jump to:

What kind of system do I have?

On-premise means you have a server on-site at your restaurant that runs your point of sale system. We have a data extraction utility installed on your POS server which runs a daily process and send task to deliver your sales data to Avero. Common examples are Aloha, Micros (3700, 9700, Simphony), Digital Dining, PosiTouch, PixelPoint, and Restaurant Manager, among others. 

Cloud Export means your POS sends us an export file containing your daily sales data, which we process. Common examples of export systems are Silverware, Breadcrumb/Upserve, Mobilebytes/Heartland, TouchBistro, Infrasys, Clover, Revel, Northstar, Salido, and others. 

Cloud API means your POS is hosted in the cloud and we access an application interface to retrieve your daily sales data. Common examples of API systems are Toast, Lightspeed, or Square. 

 

I don't know where the POS Server is / I don't have access

If you do not know where your POS server is or you do not have access to it, bring the issue to your IT department or IT servicer and they may be able to assist you by providing access or performing the data recovery for you. Once they extract the data, it will be reflected in Avero within two hours. 

If you do not have an IT department, ask your POS reseller or servicer for assistance. 

 

Sending Historical / Manual Data: On-Premise Systems

Here are the steps for recovering missing data for an On-Premise POS system. On-premise means you have a server on-site at your restaurant that runs your point of sale system. Common examples are Aloha, Micros, Digital Dining, PosiTouch, PixelPoint, or Restaurant Manager, among others. 

  1. On the PC that runs your POS, typically in your BOH, sign in as an administrative user.
    • If you don't have administrative rights, find a user that does, and ask them to complete the following steps.
  2. Open the Avero Data Extraction Utility (DEU) 
    • The DEU is typically found on the PC's desktop. If it's not, use windows to search for Avero, and you should find it.
    • The icon looks like this:
    • DEU.PNG
  3. Select the days you'd like to send on the calendar and click Run. The DEU will show 'Not Responding' while it extracts, compresses, encrypts, and transmits the data. This is normal. 
  4. The DEU will extract the files and place them in Avero's 'Output' folder and they will be transmitted to Avero after the extraction for all dates are complete. We recommend running only 2-4 weeks at a time to avoid very long running extractions. 

Please note: There is a limit to 12 months of back data sent from your system. Some systems do not hold data for that long, so check your system's POS Guide for information on how much back data you can likely extract. 

I received an error message!

Error messages are generated for a variety of reasons. After running the DEU you may see this pop-up:

mceclip1.png

Click OK to view the errors. 

Item Sales returned no data

If you have many revenue centers, it is not unusual to receive an error message even when your data has sent successfully if some revenue centers show no sales. For example, a hotel rerunning data may receive an error message 'returned no sales data' for Banquets because there were no banquet sales on that day, even though Restaurant, Bar, Mini Bar, and Room Service all exported their sales without issue. Take a look at the RVC identifier in the error message and compare it to your RVC list to identify which RVC is missing sales to know if this error is impacting your data.  

Other errors - if you see other errors or if you verify that the RVC that returned no data should have had sales: Open a ticket and our team will work with you to resolve. 

Files not transferred / Could not connect to Avero

This error is returned when the DEU cannot connect to the Avero site to relay the files. Most commonly, the cause of this is that your firewall is blocking the traffic to send these files to Avero. This may happen suddenly after a recent firewall update.

To repair, update your firewall to allow our information as outlined in Troubleshooting - IT & Technology

You can also try alternate send methods:

  • Open the Avero Data Extraction Utility (DEU) and click Options
    • Note: if Options requires a password, you'll first need to perform an update, which takes 2-5 minutes using these instructions: DEU Update On Demand
  • The DEU is typically found on the PC's desktop. If it's not, use windows to search for Avero, and you should find it. The icon looks like this:
  • Select File Transfer
  • Under 'Transport Method' select HTTP (or is already selected, attempt another format from the drop-down menu)
  • Select Apply, then OK, ​then try to send the files by selecting Send Files
  • ​
  • If successful, the data will be present in Avero in 2 hours. If unsuccessful, you can try another format or whitelisting will be required. 

Sending Historical Data: Cloud Export

Reach out to your POS vendor and request that they resend the export to Avero for each day of missing data.  Common examples of export systems are Silverware, Breadcrumb/Upserve, Mobilbytes/Heartland, TouchBistro, or Infrasys, among others. 

 

Sending Historical Data:  Cloud API

If you are missing data, we are likely already trying to recover it.  If this issue is recurring for multiple days, please open a ticket, and we'll escalate to our technical team. Common examples of API systems are Toast, Lightspeed, or Square. 

 

When Will I See My Data?

Once you or we have recovered your missing data, it still needs to load into the system. Delays vary based on how the data was received and the current load queue, so don't resend the data again as it will start over and place you at the back of the queue. You should see your recovered data in Avero in about 2 hours.

Related articles