> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/circulation-setup-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/circulation-setup-manual/distribution/print-site.md).

# Print Site

This option allows you to identify which file map is used for the stacker interface at each physical printing site. This is useful when different printing sites must use different file maps.

#### To use this option:

1. Select Distribution | Print Site.<br>

   <figure><img src="https://2165740141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5MIKWQvI2WSa0XQfA9VW%2Fuploads%2F5MyKN1OceKV04UmdvSTN%2FPrint%20Site.png?alt=media&amp;token=03642f7f-8e1b-4bb5-8dbe-62a19c816244" alt=""><figcaption></figcaption></figure>
2. Click Add and complete the following fields:
   * Print Site—Enter the ID of the physical site where printing is performed. This field is not validated; it can be any combination of characters and numbers.
   * Stacker Format—Select the stacker interface file map you wish to use at this printing site.
   * One File Per Edition—Selecting this checkbox allows the \<Edition> token of the stacker file name to be overridden, so that only one file is created, rather than one file per edition. See note, below.

{% hint style="info" %}
**Note:**&#x20;

*Using the \<Product> and \<Edition> tokens in the stacker file name allows for creating uniquely named stacker export files when publishing by edition. For example, if the file name is `<Product><Edition>stacker.dmy`, the Publication is “News,” there are 3 editions, and today’s date is September 15, 2010, the following files would be created during processing: News1stacker.150910, News2stacker.150910, and News3stacker.150910.*
{% endhint %}