Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Merchanter
English (UK)
US English (US)
GB English (UK)
  • Home
  • How to use Merchanter
  • Stock Control

Running the Rebuild of the Stock Summary if a stock count is uploaded after the period end.

Understand how to manage stock summaries efficiently by learning how to rebuild them when a stock count is uploaded post period end.

Written by Ian Oldrey

Updated at June 5th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Getting Started
    Training Sessions
  • How to use Merchanter
    Sales Invoicing & Credits Products Purchasing Stock Control OData System Settings & Administration Milling & Value Added Processing Sales Order Processing Customers System Release Updates Pricing & Costs Certification Order Picking Agency Sales
  • API Documentation
  • Integrations
    Sage 50 Woo Commerce ECS Webshop Link NearSt QuickBooks Xero ShopWired
  • FAQs
  • Industry Articles
+ More

So the stock summary (period end) is normally built at midnight at the end of a period to take the stock records as the stand and write them away.

The OData Stock Summary Rebuild Utility can be run by Ten-25 for you to update the month end figures to account if a stock count was counted before the period end, but not uploaded until after the period end.

When we do the period end rebuild it takes the stock as it is today and uses all the physical stock movements to work back to what the stock would have been at the period end, based on today's figures.

So following a timeline of events for one product at one depot as an example:

  1. System shows there are 8 buckets in stock on 25th April
  2. A count is done on 26th April for 12 buckets, but not uploaded
  3. In the days from stocktake to month end 3 are purchased and received, and 4 are sold and supplied.
  4. At midnight of 31st April the system writes away a period end stock summary of 7 buckets (8 stock + 3 in - 4 out)
  5. In the week after the 31st 10 more are purchased and 3 more are sold.  So the stock on 5th May shows as 14 buckets (7 buckets + 10 in - 3 out)
  6. The stock count is uploaded on 5th May
  7. The system calculates from 14 buckets today back to 26th April that 14 buckets less all the movements the stock was 8 buckets, but the count was for 12.
  8. It either puts in an adjustment in for 4 buckets, or zeroises 8 buckets and puts in a count of 12 buckets.
  9. So the stock on 6th May will now show as 18 buckets (14 + count adjustment of 4 historically)
  10. When we then run the OData Period End Rebuild, that takes the 18 buckets now in stock, reverses the May movements (- 10 out and +3 in) and writes away that the stock would have been 11 buckets at the end of April.

So with that example, you should now have a count record for 26th April for 12 buckets, a movements report that says 3 came in and 4 went out between 27th and 31st April, and a period end stock summary that says you had 11 buckets at the end of April (the year).  

If you don't run the rebuild the Stock Summary report shows that you had 7 buckets at year end rather than 11.

rebuild update

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Stock Counts
  • What are Stock Location Count Types?
  • Managing Minimum (Min), Target and Maximum (Max) Stock Levels on a product/depot
Solution Vendor Color.png

sales@ten-25.co.uk

01202 861606

Peartree Business Centre, Cobham Road, Ferndown, BH21 7PT, United Kingdom

BMF Service Member logo.jpg
  • linkedin
  • twitter
  • facebook
Privacy Policy

©2020 by Ten-25 Software Ltd.. Proudly created with Wix.com

Expand