Help Center

Primary source: Batch Count (aka Page Size)

Sarah Bacchus
Sarah Bacchus
  • Updated

Everything you need to know about pagination

To make sure we’re on the same page, let’s start by looking at pagination.


What is pagination?

Have you ever clicked through an image gallery? Or read through an extensive web tutorial broken up into multiple segments? Do you know the numbers on the bottom of the gallery or webpage?

That’s pagination., a technical SEO website, defines pagination as “an ordinal numbering of pages, which is usually located at the top or bottom of the site pages.”

Data transfer pagination just applies that principle to the realm of data transfer protocols like API.

Batch Count is the "page size" or "number of records per page" in our request for product data

API queries to dense databases could potentially return millions, if not billions, of results. There’s no telling what kind of drain that could put on your API server. Pagination thus helps to limit the number of results to help keep network traffic in check.


Primary Source Settings

You will find an option for Batch Count on mostly all of our import source types. This option refers to the number of records per page or page size of the download request when we import product data.

Whether you are using GoDataFeed XML or we are importing your products via API from Shopify, BigCommerce, WooCommerce, Magento, and so on, you have the option to control the Batch Count or the number of records per page. 


Default Batch Count

When nothing is selected from the dropdown, then we default to 100 or another amount for different sources. 


Source Default
Default value 100
MagentoSOAP 100
MagentoREST 100
WooCommerce 100
Shopify 250
BigCommerce 250
3DCart 250
Oracle 250
NetSuite 250


Import time is affected by batch count

The Batch Count is used during the download to control the page size of our request. For smaller servers, this option allows us to keep our requests smaller although this may extend the total time to complete a full import. 


Reduce batch count for smaller servers or high-traffic times

"The remote server returned an error: (500) Internal Server Error."

Consider lowering the batch count if you get 500 Server Errors. Data requests add traffic to a server. Large pages of data require more resources. Whether a server is small or it's a high-traffic time, reducing the batch count, or page size, can help prevent import failures.


Adjusting Batch Count

To modify the batch count

  1. Navigate to Import > Primary Source
  2. Select the Batch Count drop-down
  3. Choose the batch count size
  4. Save your changes
  5. Click Import to start a new import

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.