What are the standard specifications of a BookRouter™ export file and how are images handled?

What are the standard specifications of a BookRouter™ export file and how are images handled?

BookRouter™ creates a standard inventory file for all marketplaces that support File Transfer Protocol (FTP). This includes AbeBooks, Alibris, Antiqbook and Biblio, Inc. Standard BookRouter™ files are tab delimited text files with a .txt extension.

Note: BookRouter™ manages your Amazon and eBay inventories via Application Programming Interface (API). viaLibri uses an xml feed to manage listings on individual Bibliopolis websites. This article does not apply to these marketplaces.

BookRouter™ Standard Export Format: The first record in all upload files sent from BookRouter™ is a header record with fields in the following order:  

sku
author
title
subtitle
place_pub
publisher
date_pub
edition
isbn
description
binding
condition
jacket_cond
comments
dj (y/n)
signed (y/n)
first_ed (y/n)
illustrator
keywords
subject 1
subject 2
subject 3
subject 4
subject 5
alt_1
alt_2
type
* image_url 
price
quantity   (0 = delete; > 0 = add)

 

* image_url BookRouter™ populates the image_url field with the primary image URL with exceptions for marketplaces that support multiple images per listing. In these instances, the image_url field contains comma separated image URLs.

Marketplace specific image_url specifications:

  • ABE upload files contain up to their maximum supported five image URLs.
  • Alibris upload files contain a single image URL.
  • AntiqBook upload files contain a single image URL.
  • Biblio upload files contain all image URLs.