Sales history by SKU in B@SE

Re-phrasing an earlier question: Anyone found a way to get sales history by SKU using B@SE? I had in mind I could get a list of orders by SKU and filter by date range, but anything that lists orders (such as thumb_list) seems to revolve around customers not skus, and won't work without the context of a user session. Surely sales/orders by product is a supported data set in B@SE?

We're essentially trying to make a custom forecast demand report that actually works using data export templates. The Neto forecast demand report is no good for our requirements, and is not very well thought out at all.

Find more posts tagged with

Accepted answers

All comments

Erik Merkley

B@SE can't do this directly. It's not able to generate reports since it's geared towards front-end website templates. There is one field which might help: [@quantity_sold@] is the all-time total sales of that SKU. Combining that with [@created@] can be useful.

To do real stock forecasting, your better option is to export *orders*, not products. Dump out the entire order history for the period you are interested in. Then just use Excel to total up the sales per SKU. This gives you vastly more data and you can do much more sophisticated modelling.

Alternatively, the Forecast Demand report itself is exportable to CSV. If you also do an export of products with incoming qty, you can combine them in Excel to take that incoming stock into account. PowerQuery is great for building reports once and then re-loading fresh data each time from CSV.

If you are a large business and need better stock forecasting, it's worth looking into the network of Neto Partners. Several partners have built analytics systems that pull all your sales and product data out of Neto into an external database which makes any sophisticated reporting possible.

Dan H

Some interesting ideas there. Our purchasing staff are currently doing all kinds of spreadsheet wizardry to produce usable data from Neto exports, but it's labour intensive and error prone and we want to streamline the process. We do all our development in house, but naturally, we try to use the existing Neto functionality we're paying for as a priority. Thanks for the suggestions.

Dan H

@Pranay Shinde , as a developer who spends a lot of time working with the Neto platform, I really wish Maropost would put someone on the API and it's documentation. At an absolute minimum, the addition of purchase orders to the API would make building custom systems like this a relatively simple task. And noooo... I'm not going to put that on the ideas portal as it's pretty clear no one from Maropost reads it! 😬 Please send that up the chain fwiw

Erik Merkley

Yeahh we all want Purchase Order APIs. They were on the roadmap for years, then they became a priority and development actually started. Then it was suddenly abandoned (along with the new Forecast Demand report that would do everything you need). Development is focusing on the "new platform" so Neto is languishing unfortunately.

Deactivated Member

Hi @Erik Merkley and @Dan H.

I hope this message finds you well. I appreciate your valuable input. I reached out to our product manager to address your concerns, and I have some updates.

Firstly, I want to emphasize that we are actively monitoring the ideas portal, and we've recently implemented some of the top ideas. One example is an API-related improvement, and the team is working on another significant idea in the pipeline, set to be launched next week. Additionally, we are working on the highly requested Margin Calculator on POS.

Regarding the Purchase Order API, I’d like to inform you that it already exists within our V2 API. During the "Neto's Next Wave" webinar, we mentioned our plan to release the public V2 API this year, targeting Q2/Q3. While I can't make any definitive promises about specific endpoints, I can confirm that the Purchase Order API is part of the discussion, as seen in the provided screen below. MicrosoftTeams-image (15)

Now, addressing the Reordering Report mentioned by Erik, I want to acknowledge its importance. Unfortunately, we had to temporarily put it on hold due to prioritizing other Neto-related projects, including crucial technical upgrades.

Please be assured that we remain fully committed to Neto, with separate teams dedicated to both the new platform and existing Neto functionalities. While there are challenges, these efforts are vital to ensure the growth of the Neto platform .

Thank you for being an integral part of the Neto community, and please feel free to reach out if you have any further questions or suggestions.

Best regards.

Scott Marett

@Dan H , I have an advanced Business Intelligence platform that synchronises all of your Neto data one way using the Neto API (all Get calls) and in addition have a process that synchronises Purchase Order data as well.

Feel free to reach out to me to discuss further.