implementations of the invention include interrelated elements . these elements and their relationships will first be discussed briefly and then later in more detail . an implementation of a print job management system 10 is shown schematically in fig1 , 1 a , and 1 b . a potentially enormous number ( e . g ., thousands or even hundreds of thousands or millions ) of individual and commercial customers 12 , wishing to place orders for discrete printjobs ( generally short run printing jobs , i . e ., jobs of less than 40 , 000 units , typically 250 - 5 , 000 units ), access the internet 14 via web browsers 13 ( or similar interactive communication software ) running on personal computers or other electronic devices 11 . customers can access the system through any one of several different types of entry ports 15 into the print job management system , where some types of entry ports may be characterized by their economic and market characteristics . the types of entry ports could include home office / small office computer entry ports 15 a , intermediary ports ( such as boutique stationery stores ) 15 b , and large corporate entry ports 15 c ( such as a communications department of a large corporation ). other entry ports need not be based on web browsers , but could be , for example email links 15 d and dial up voice telephone lines 15 e . the system can also be integrated with bidding systems or “ ehub ” bidding sites such as noosh , impresse , collabria and ariba ( ehub portals 15 f ). the term “ print job ” refers to an individual print job , such as a single design version of a brochure for a business in a given quantity such as 1000 brochures . the term “ order ” is used to refer to a group of print jobs that are ordered at the same time , such as a business card , letterhead , and envelopes for a business . for some customers , individual print jobs could be part of a large corporate communication program that would include hundreds of different documents each bearing common graphic elements and custom text associated with each document . through the internet 14 , each customer can access a website 16 , that includes a website studio 16 a which provides design software that is made available from a central web server 18 . the website studio , which will be discussed in further detail below , allows each customer to design one or more custom printing jobs , e . g ., business cards , brochures , postcards , folders , letterhead , and envelopes . the customer chooses from a limited selection of standardized papers , formats ( provided to the user in the form of templates with user - specified data fields ), colors and quantities . the website studio software is downloaded from the server as part of web pages displayed to the user , runs on the user &# 39 ; s browser , and enables the user to perform simple design functions by completing a selected template using a design wizard , or more complex design functions using a design studio , locally on his browser . typically , only the results of the design process are uploaded to the server as a print job . the templates are created using an xml format or other appropriate format . alternatively , a customer or a professional designer could generate his own template , using the website studio itself , or using desktop publishing software , and upload it to the server website studio . as shown in fig1 , two kinds of data pass back and forth between the customers and the system , and there are two series of processes that handle this data . the data can be categorized as graphical print data 115 ( in fig1 , graphical print job data 117 , templates 119 and web studio software 121 ), and commercial print job data 123 . processing of this data is split into two pieces : what goes on between the customers and the system , shown in fig1 a , and what goes on between the system and the printers , shown in fig1 b . as shown in fig1 , there is storage at various points in the system to store the data . for example , some of it is stored in the customer &# 39 ; s pc storage 111 , some in the system &# 39 ; s data storage 20 / 22 , and some at the printer data storage 113 . the system &# 39 ; s data storage is shown in more detail in fig1 a . the data input by a customer when an order is placed is stored in a central database 20 and / or a network storage 22 , depending on the nature of the data , as will be discussed below . the network storage 22 stores all of the graphic files that define a print job , e . g ., logos , fonts , backgrounds , layouts and frame designs , while the central database 20 stores , among other things , all of the non - graphical information , e . g ., the text to be printed and the business information that is needed to get the jobs printed and delivered . the central database 20 also stores information regarding the customer , e . g ., the customer &# 39 ; s name and address , and stores the non - graphical elements of the website studio templates ( the graphical elements that are stored in the network storage are referenced by the templates and document layouts ). once the customer has finished designing the print job the customer places an order , e . g ., using a purchase wizard 16 b , as discussed below . the customer &# 39 ; s print job is sent to the server in xml format , and the xml file is then converted by the server into a digital format , e . g ., into a postscript file 128 ( fig1 b ). the backend printing servers 28 then automatically aggregate , or “ gang together ”, the customer &# 39 ; s postscript file with multiple postscript files from other customers to produce a consolidated print sheet ( a “ layout ”). to achieve this , the backend servers assemble the individual postscript files to create the layout 130 ( fig1 b ), with different individual print jobs arranged on respective portions of the layout . for example , as shown in fig2 , 133 different business card print jobs 50 of identical size could be aggregated into a layout and printed on a single large printing sheet 52 , e . g ., a large format printing sheet measuring 1 . 0 meter by 0 . 6 meter . in other examples , different sizes and shapes of print jobs can be aggregated , e . g ., as shown in fig2 a and discussed below . the organization of the different print jobs on the layout 130 is defined by aggregation templates that characterize where cuts need to be made after printing in order to separate the different print jobs . the choice of which print jobs to place onto a given layout and in what arrangement is discussed below . the commercial information related to the customer &# 39 ; s order ( e . g ., the shipping address , shipping date , etc .) is stored in a customer information file 132 ( fig1 b ). the customer information file 132 is aggregated with other customer &# 39 ; s files ( the same customers whose postscript files have been aggregated onto the layout ), to create an aggregate meta file 134 which contains all of the commercial information for the customers &# 39 ; print jobs . the aggregate meta file 134 also includes commercial information relating to the printing run , e . g ., a batch number (“ template layout reference number ”), the number of sheets to be printed , and the cutting template to be used to cut the printed sheets into individual printed print jobs . the aggregate meta file is posted by the backend server to a website 136 that is accessible to printing firms 138 wishing to sell their printing services to the web server host . the aggregate meta file 134 includes the commercial details of the print run that will be performed using the postscript layout file 130 ( e . g ., number of sheets , type of paper , and deadline ). as will be discussed below , printing firms with unused capacity bid for a contract to print the print run . generally , the contract is automatically awarded to the bidder providing the most competitive bid based on predetermined criteria , e . g ., lead time , quality , history , price or other factors . the successful bidder &# 39 ; s contractual obligations , and the postscript layout file and aggregate meta file , are then transmitted by the backend server to that printing firm , e . g ., to a server 32 located at the printing site . the postscript layout file is converted at the printing facility 29 , during riping ( raster image processing ), to the color separated prepress format that is used by standard computer - to - plate systems that produce four - color photolithographic plates 110 ( fig1 b ) for use on automated large scale offset printing presses 30 . by large scale offset printing presses we mean either ( a ) sheet - fed presses with sheet formats of 530 × 740 or larger and straight printing rates of 12 , 000 sheets per hour or higher , or ( b ) web presses with roll widths of 20 inches or higher and printing rates of 40 , 000 iph ( inches per hour ). large scale offset printing presses include , e . g ., heidelberg , speedmaster , and other similar or larger printing press production systems .) the server 32 provides a browser interface for use by people who operate the printing presses (“ print operators ”). information about how to set up and perform each of the print runs is provided in a simple format to the print operators through the browser interface , as discussed below . the plates are used to print a desired number of copies on a standard printing paper that is loaded by the print operator using standard four - color process inks , based on meta file information that is provided by the backend printing server to the operator on a web - browser based computer display 32 at the operator &# 39 ; s station . the printed sheets are then transferred to a cutting station 140 ( fig1 b ), where they are cut and sorted into individual print jobs 142 , as will be discussed below . in some implementations ( such as for presentation folders or envelopes ) additional post - print processing is performed such as folding and / or gluing . the orders are then immediately shipped to the respective customers , using shipping information that is displayed on a computer display 34 in the shipping area of the printing facility . most customers “ pre - pay ” ( e . g ., provide their credit card billing information ) upon placing their orders . some corporate customers may be invoiced . generally , the customer &# 39 ; s credit card is not debited until after the customer &# 39 ; s order has been shipped . the backend printing server sends a meta file 144 back to the web server after a shipment has been made , informing the web server of the status of each customer &# 39 ; s order . once an order has been successfully shipped , the backend server interacts with a processing center 146 so that the customer &# 39 ; s account will be debited , or , in the case of a corporate customer , sends the corporation an invoice . the only requirement for use of the print job management system by a customer who is accessing the system through one of the types of browser - based entry ports described above is a computer that is linked to the internet by a standard recent web browser , e . g ., microsoft internet explorer 4 . 0 or higher . the customer accesses the website 16 by entering the website url address into the browser . other entry ports do not even require that the customer have access to a browser , e . g ., a dial - up voice telephone link 15 e could be used to enter information by voice or punching keys on the telephone keypad . the design and order process is conducted through the website . the rest of the system is “ invisible ” to the customer . the customer &# 39 ; s order is printed and delivered to the customer without any requirement for further interaction , although the customer may use the website to track the progress of the order through the printing process and the shipment of the order to the customer . the website studio allows the customer to design his own print job , using the browser for design selection and editing . the website studio uses a user - friendly “ what you see is what you get ” (“ wysiwyg ”) functionality that allows the customer to choose a base design for a desired printed item ( e . g ., business card or stationery ), and then edit the design . the functionality is similar to that of existing desktop word processing publishing products , making the website easy for most customers to use . as shown in fig3 , using the browser and the design wizard portion of the website studio the customer can choose a printed item from a wide selection ( e . g ., business cards , letterhead , invitations , brochures and marketing materials ), choose basic options such as page orientation ( portrait or landscape ), view a variety of design templates that are available for the item and choose one , complete the template ( e . g ., by supplying new text , uploading graphics files and adjusting fonts ), and save the resulting design . the customer can then add the item to his shopping cart , place an order , or perform further design modifications using the design studio portion of the website studio . the design process will be described in further detail below with reference to fig4 - 4o . once the customer is satisfied with the design , the customer can add the design to his shopping cart as a print job , and use the purchase wizard , discussed below with reference to fig4 p - 4w , or other purchase function , to place an on - line order and pre - pay for the order over a secure connection . the customer is offered a relatively limited selection of standard papers , to allow easy and cost efficient aggregation of print jobs and printer set - up , as will be discussed below . customers also select from certain predetermined print quantities , e . g ., multiples of 250 units ( 250 , 500 , 1000 , etc .). the procedure described above would be followed by a customer entering the system from his individual pc . if other entry ports are used , for example an intermediary port 15 b , some of these steps may be bypassed , e . g ., the customer may not use a purchase wizard to place and pay for the order . fig4 - 4o show webpages from a website studio used in one implementation of the invention . to begin the design process , the customer first navigates from a home page ( not shown ), to the design wizard ( fig4 - 4 e ). the design wizard is configured to appear to the customer like a standard windows ® wizard application , e . g ., with “ back ”, “ next ” and “ finish ” buttons , giving the customer a feeling of familiarity and user - friendliness . in the design wizard , the customer selects the item that the customer wishes to design ( e . g ., business cards or other items , in fig4 - 4 e ). for business card design , the design wizard includes a welcome screen ( fig4 ), an orientation screen ( fig4 a ) that allows the customer to choose between horizontal and vertical cards , a template browser screen ( fig4 b ) that allows the customer to choose between a variety of different design templates ( not shown ), an information screen ( fig4 c ) at which the customer fills in a number of fields to complete the selected design template with the customer &# 39 ; s information , and review screens ( fig4 d and 4e ) that allow the customer to review the front and back of the resulting business card . after reviewing the card , the customer can decide to ( a ) go back and edit the card , ( b ) go to the checkout ( the purchase wizard described below ), or ( c ) go to the design studio to perform more complicated design functions ( e . g ., changing fonts and color schemes ). a design studio used in one implementation of the invention is shown in fig4 f - 4o . when the customer opens the design studio , the customer will first see an initial screen ( fig4 f ) with a loading bar , indicating the status of the downloading of the design studio to the customer &# 39 ; s browser . each time something ( e . g ., a font ) is downloaded to the customer &# 39 ; s browser from the web server , a similar loading bar will be provided . the design studio is configured to have toolbars and other features that are similar to those used in standard word processing and desktop publishing user interfaces , so that again the customer will have a feeling of familiarity with the software and will find the software easy to use . in the case of the loading bar , the user is comfortable with the notion that the application is loading even though it is not being loading in the usual sense of being moved from a hard disk to memory in the user &# 39 ; s computer . the design studio also includes a standard “ startup tips ” dialog box ( fig4 g ), like other windows ® applications , and a help system . in the design studio , the customer can select a background from a variety of choices ( fig4 h ), use a “ picker ” dropdown list ( fig4 i ) to select other design features ( logos , card layouts , color schemes , designs and fonts ), modify those design features , add a logo ( fig4 i ), select a color scheme ( fig4 j ), change the color of selected text ( fig4 k ), change the properties of an image , e . g ., the logo ( fig4 l ), view the backside of the card ( fig4 m ), and preview exactly how the front and back of the printed card will look ( fig4 n and 4 o ). the design studio features in - place editing , i . e ., the customer can double - click on an item and change it directly . while in the design studio , the customer can make as many modifications to the fonts , colors , card layout , etc ., as desired . the customer can also choose to view the design at low resolution , medium resolution or high resolution . in some implementations , the customer can add text or graphics to the back of the card , in which case in most implementations the existing “ advertisement ” text is automatically removed and this removal is automatically chosen as a purchase option in the purchase wizard . the customer can also choose a blank back side as a purchase option . if desired , a customer using the design studio can upload a graphic file , e . g ., containing the customer &# 39 ; s logo . the file can be , e . g ., created using graphic design software , downloaded from the internet , taken with a digital camera , or scanned in with an image scanner . generally , the file should have a relatively high resolution , e . g ., at least 300 dpi . most standard graphics file types are supported . the customer &# 39 ; s graphic file is stored in network storage 22 , and is referenced by the xml file created by the customer in the website studio and added to the postscript file for the customer &# 39 ; s print job when the postscript file is created . when the customer is satisfied with the design of the card , the customer can proceed to the checkout ( the purchase wizard ), or can save the finished design ( the customer &# 39 ; s print job ) for later purchase . in either case , the customer &# 39 ; s print job is saved in xml format in the central database 20 . the xml file includes the size and orientation of the document , the number of pages , and , for each page , the margins , background , frame design ( if any ), and the text and graphics elements on the page and their characteristics ( color , font , size , etc .). the website studio is designed for use by customers who have no graphic arts experience or specialized software knowledge , e . g ., small business owners who want to “ do it all ” and workers in companies whose goal is to update information , such as the company address or telephone number , prior to ordering or reordering printed materials . for users with graphic design experience and desktop publishing software , the web server provides a full toolset that is compatible with leading desktop publishing software such as quark express and adobe indesign software . thus , a print job can be designed by a graphic artist , using professional desktop publishing software , and then uploaded to the web server for distributed access to other users at the customer company . for example , the graphic artist can define fixed and variable fields , and an administrator or other designated employees at the company can then be given access to input information ( e . g ., company address and telephone ) into the variable fields , without changing the fixed fields ( e . g ., the overall design and graphics of the print job ). as a result , customers having access to desktop publishing software can create their own templates , rather than being limited to the templates offered by the web server host . when the template is uploaded to the web server , it is split into graphic data ( logos , fonts , backgrounds and designs ) and all other data . the graphic data remains in its original format and is stored in network storage 22 , as discussed above . the remaining data and layout information is converted to xml format and stored in the central database 20 . unlike other previous , server - based approaches , the website studio utilizes browser - based processing to allow high - speed processing when the customer is working interactively to design a print job . the website studio utilizes javascript and dhtml technologies for the graphic design by the customer , i . e ., the web pages that the customer receives and views include not only the static visual display , but also graphic design programs ( the website studio ) that will run on the customer &# 39 ; s browser just as any other application runs on a computer . thus , the customer can use the browser interface to do graphical design without interacting with , and thus consuming the resources of , the web server . so that the website studio can be quickly downloaded by the customer , in most implementations the graphic elements , e . g ., fonts , backgrounds and logos , used in the website studio are stored in a library in the network storage 22 , a copy of which is stored at the printing firm information system 29 , as will be discussed below . thus , a graphic element need only be downloaded by the web server to the browser when it is selected by the customer during the design process . the xml file that results from the design process ( the customer &# 39 ; s print job ) will reference the appropriate information in the centrally stored library . the library is replicated at the printing firms , so that the graphic elements can be inserted during riping using opi ( open prepress interface ) techniques . the library can be distributed periodically using a cd - rom publication or other distribution approach so that all parties to the system are working from the same library . post - design processes , such as high resolution proofing and processing files , are queued separately and processed by the backend servers independently of the web server , because the customer is not waiting for these processes to be completed and thus processing speed is not a concern . the web studio may also include a dynamic shopping cart , which allows the customer to access the shopping cart at any time during the design process to add or delete items . the web studio application is based on modules , to provide an open development architecture . different modules are plugged into the core libraries to provide additional functionalities , e . g ., the undo / redo history manager is a separate module that could be deactivated , by removing a few links , or replaced by a new and more powerful module complying with the same architecture as the current module . the web studio application uses style sheets to “ style ” the interface into a usual windows ®- like interface . using style sheets allows the application to have a smaller overall size , as styling policy is centralized in a few modules that are reused in the application &# 39 ; s web pages . providing a centralized styling policy also allows the web server host to change the look and feel of the web studio interface at any time , just by changing the styles . in one implementation , the modules use internet explorer xml dom implementations . using these functionalities , a real - time renderer can be created which will take any xml document and , using xml style - sheets ( xsl ) transform the document into a wysiwyg preview . the use of these integrated functionalities allows a small and fast rendering / edition engine . using htcs ( html components ), scalability and processing speed can be enhanced . also , the web studio application can be designed to behave differently on the result of the xsl transformation , just by using a different previewing style sheet ( css ). thus , after rendering , the resulting preview can be a simple “ flat ” preview , or an editable document that the user can interact with . if the xml document model is extended to vml ( vector markup language ), the web site studio is then able to render documents created by most common office applications , e . g ., microsoft word . the user can then modify such a document and send it to the webserver for printing . this feature enhances the compatibility of the web studio with usual windows ® applications . extension of the xml document model to vml also allows the web studio application to draw more complex shapes ( e . g ., ovals , rounded rectangles and curves ), apply color gradients and color schemes to complex objects , and use transformations , making it possible for a user to design and print complex documents to suit his or her needs . a purchase wizard used in one implementation of the invention is shown in fig4 p - 4w . like the design wizard , the purchase wizard appears to the customer as a standard windows wizard application . the wizard may be configured to run on the user &# 39 ; s browser , or on the web server , depending on the preference and resources of the web server host . the final purchase information is transmitted over a secure server connection . the wizard includes a welcome screen ( fig4 p ), a review screen ( fig4 q ) that gives the customer a final opportunity to review the design , an address screen ( fig4 r ) that allows the customer to input a shipping address and select an order quantity , one or more options screens that offer the customer choices of upgrades , e . g ., to remove the advertising text on the reverse side ( fig4 s ), a delivery screen ( fig4 t ) that allows the customer to select delivery options , e . g ., expedited delivery , a screen that notifies the customer that the order is being submitted to the server ( fig4 u ), a billing information screen that allows the customer to input billing information ( fig4 v ), and a payment confirmation screen that asks the customer for final confirmation of the order . once an order has been placed , the server stores the customer &# 39 ; s order information into the central database 20 , including the commercial information regarding the customer &# 39 ; s order . in some implementations , relatively low cost items , e . g ., business cards , are offered to customers by the web server host at no charge . the cost of printing these items can be recouped by the web server host by charging a fee for upgrades , e . g ., faster delivery , and sales of complementary items such as business card cases . for example , as discussed above , the web server host may include an advertisement ( e . g ., “ free business cards at www . vistaprint . com ”) on the back of each free card , and charge a fee if the customer does not wish this advertisement to appear on the customer &# 39 ; s cards . for all orders , the web server host may , if desired , charge additional fees for enhancements such as expedited service and gloss or other special finishes . customers can obtain support through the website by visiting a faq (“ frequently asked questions ”) or help page ( not shown ). in some implementations , the website will also offer interactive online support , support via email , and / or a toll - free number that customers can call for telephone support . if desired by the website host , access to interactive online support , email and telephone support may be restricted to certain preferred customers , e . g ., corporate customers having accounts with the website host . alternatively , the website host may offer these services to all customers at no charge or may charge a fee for access . as discussed above , the customer can access the website studio using his own computer and browser , or can use another type of entry port , e . g ., an intermediary port 15 b ( such as a terminal at a boutique stationery store ), or a large corporate entry port 15 c ( such as a communications department of a large corporation ). the entry port need not be based on a web browser , but could be , for example , an email link or dial up telephone line . the customer may use the website studio without assistance , or may describe the desired print job to someone else , e . g ., a graphic designer or salesperson at the boutique stationery store , who will use the website studio to design the print job . in some types of entry port , the web server provides the interaction of the customer with the web studio . the web server uses a typical three - tier architecture to respond to all of the customer page requests , by using server - side scripting to access server objects that implement the business logic , these objects in turn interacting with the central database and network storage to access the necessary data . hundreds of thousands ( potentially millions ) of customer relationships are managed by the system . each customer order typically involves a relatively large file due to the nature of color graphic printing data . the data storage capacity of the system is robust enough to handle high levels of data storage and data access . the data storage is also capable of acting as a link between the front end at which orders are placed , the design studio , the backend printing servers , and shipping , accounting and marketing systems . a data storage system that is capable of meeting these requirements is an oracle rdbms running on a unix box or a microsoft sql server 7 . all data is stored in either the central database 20 or the network storage 22 . stored data includes business - related information such as information pertaining to customers and orders , and design data specific to each customer &# 39 ; s print job . network storage 22 includes one or more network attached storage ( nas ) systems , and is configured to store all graphical objects that are used by the design wizard and studio and that are uploaded by customers , including logos , backgrounds , fonts and frame designs . the network storage includes a library , which contains all of the backgrounds , logos and fonts that are used by the design wizard and studio . customer uploaded information is not stored in the library . the library is replicated and sent to each of the printing firms used by the system for print runs , and the contents of the library are referenced by the postscript layout files sent to the printing firms . the network storage may also contain the web pages used in the website 16 . a very large amount of data is stored in the network storage 22 , e . g . up to several terabytes depending on the number of customers using the system . the network storage 22 is completely server independent ( it includes its own enclosed cpu ) and is directly connected to the local area network ( a local area network internally operated by the web server host , including the web servers , the backend servers , and the storage devices ), making the stored data available to connected servers , i . e ., the web server ( s ) 18 and the backend printing servers 28 . as of the writing of this description , a single nas system can typically handle from 20 gigabytes to one terabyte of data . thus , as data space needs increase more disks can be added to the nas ( this operation typically does not require a service shutdown ), or , when the limit of each nas is reached , an additional nas can be added to the system . as shown in fig5 , the web servers , central database , and backend servers are connected to the network storage by an ethernet . central database 20 is a relational database management system ( rdbms ) that handles all non - graphical data . this database is designed to handle millions of records . as is customary , the data is organized in tabular form . in one implementation , the database includes the following tables , which include the listed fields . ( more , fewer or different tables may be used in other implementations , as needed .) unique print job id and name , xml content of print job , sku name , quantity of print run , action to be taken when layout is data stays in the database as long as it is needed by the system . data is maintained in the orders table after a customer &# 39 ; s order has been completed and shipped , to facilitate reordering . to avoid overloading the database , the web server host may place a time limit on reordering , or charge the customer a nominal fee for keeping his information in the database for an extended period of time . each time a layout is created , an entry is created in the layouts table . depending on the action to be taken , the print operator may be notified by email , or an extranet query can be set up to query the table , or a process may be running at the printer that checks the table for new layouts . the following status codes may be used in the “ status ” field in the orders table : status code value status description st_ready 0 the order has been submitted by the customer but at this point has not been processed . st_processing 1 this order is being processed . st_cancelled 2 this order has been cancelled . st_repeat 3 there was a problem with this order so it has been re - submitted . this code is treated by the system in the same way as an “ unprocessed ” order . ( re - submitted orders can only be re - submitted a few times before a warning is raised ) st_dispatched 4 this order has been dispatched and the tracking information has been updated . st_completed 5 the customer &# 39 ; s credit card has been charged . this order has now been completed . prepress aggregation is performed by a prepress aggregation module of the backend printing server , which includes a multi - user postscript file creator , shown as item 200 in fig8 . the file creator collects all of the print jobs that have been received by the web server and queued for printing . the file creator includes four queue - processing components , as follows . the first component 202 creates individual postscript files 204 for each customer &# 39 ; s design , and individual meta files 206 , referenced to each customer &# 39 ; s postscript file , that contain job tracking information and other commercial information related to the customer &# 39 ; s order . the second component 208 collects these postscript files , according to aggregation parameters ( e . g ., job tracking information and size of the printing paper to be used ), and aggregates ( or “ gangs ”) them to produce a postscript file 210 that contains “ n - up ” designs , the value of n being dependent on the design size , the paper size , and the exact layout required due to requirements such as edge bleed . the third component 212 does an automatic “ pre - flight check ” on each aggregated postscript file , thus avoiding the need for further manual intervention . the fourth component 214 optimizes production scheduling and routes the final aggregated postscript file to a raster image processor ( rip ) 220 at the printing cell . the print jobs are arranged spatially on the master , rather than in chronological order . as a result , several types of items can be aggregated and arranged on a single layout , e . g ., postcards , invitations and business cards . for example , as shown in fig2 a , the layout can include business cards 50 , postcards 53 and invitations 55 . if any of the aggregated print jobs are to be printed on both sides , the entire layout will be printed on both sides , with blank areas for any print jobs that are printed only on one side . some items , e . g ., envelopes , generally cannot be aggregated with other types of items because of their specific post - press processing requirements . aggregation may be performed in accordance with one of a number of standard aggregation templates , as noted above , or can be done “ on the fly ”, in any arrangement that will fit within the bounds of the paper sheet to be printed . the prepress aggregation module , a rules - based program , aggregates print jobs by scanning the ordered items table of the central database and searching for items ( print jobs ) that have the same printing requirements , e . g ., the same delivery date , paper grade , and post press processing requirements . scanning generally continues until enough print jobs have been located to fill a layout of a given size . the xml files corresponding to the selected printjobs are then pulled from the document table , converted to postscript files and aggregated , as discussed above . printing is generally performed in a base print run of a standard number of sheets , e . g ., 250 sheets . the prepress aggregation module automatically deals with a print quantity that is greater than the number of sheets in the base print run by allocating that print file to one or more extra position ( s ) on the consolidated sheet ( master ). for example , if the base print run is 250 sheets and a customer orders a print quantity of 500 , the customer &# 39 ; s design would occupy two positions on the master , whereas if the customer orders a print quantity of 1000 four positions would be occupied . the prepress aggregation module is also able to differentiate between these different quantity orders , and thus when sufficient order volume is being generated at , e . g ., 500 units , the module will create a print file with each order occupying only a single position and increase the base print run to 500 sheets , further reducing unit cost . also , in the unlikely event that insufficient orders are received over a period of time , one or more position ( s ) on the master may be left blank . in some implementations , the prepress aggregation module is configured to provide digital management of queues to allow a customer to choose to have his order expedited for an additional cost . expedited orders are queued ahead of non - expedited orders , so that non - expedited orders will be printed later , e . g ., 5 - 7 days later , than expedited orders which are printed immediately . as a result , all orders can be shipped immediately after printing , without the need for the printing firm to sort out and hold back non - expedited orders . if there are a few particularly high priority jobs waiting to be printed , the program with aggregate these jobs and send them to be printed immediately , without waiting for enough orders to be received to fill a layout . the backend printing servers do not interact directly with the customers . the backend printing servers do the processing ( e . g ., print job aggregation and printer preparation and optimization ) that occurs after the customers have designed the print job and placed orders . generally , communications between the backend printing servers and the print subcontractors are handled over dedicated leased lines due to the high volume of real - time data transfer from the backend print servers to the print production floor . after the print jobs have been aggregated and queued by the prepress aggregation module , as described above , the resulting layout and aggregate meta file are sent by the backend printing servers to designated printing firms . the printing firm to which the data is sent may be selected by an automated bidding process , which will be described below . the digital data is then used to make color - separated offset printing plates in accordance with the layout . the printing plates are generally prepared in advance of the time allotted for the print run , e . g ., the layout and meta file are sent at least an hour before the scheduled print run and the plates are formed immediately ( plate forming generally takes about 10 - 15 minutes or less ). once the printing plates have been formed , the operator of the printing press loads the specified grade and quantity of printing paper for the aggregate print run , e . g ., 250 sheets plus “ overage ” for a 250 sheet run of business cards . for this purpose , the operator refers to a browser - based terminal at his work - station , which displays information from the meta file concerning the print run . the print run is then performed , resulting in the desired number of printed sheets , e . g ., a stack of 250 printed sheets for a 250 sheet run . the system can organize multiple aggregate print runs that use the same paper base , thus eliminating the need for paper changes . referring to fig1 b and 6 , there are several steps that take place after a print run . these steps include cutting , post - forming ( in some cases ), sorting , packing and shipping . these steps are described in detail below . print jobs that are part of an order ( e . g ., letterhead ) can be held until other print jobs that are part of the same order ( e . g ., envelopes ) are ready . ( in some cases , the different parts of a customer &# 39 ; s order may be printed at different printers , in which case they will be shipped separately .) in some cases shipments may also be tracked and customers informed of the location / status of their orders . to cut the stack of sheets into individual customers &# 39 ; print jobs , the operator selects an appropriate template by again referring to the terminal information , and / or by referring to a batch number ( or “ template - layout reference number ”) on the printing plate or printed in the margin area of the printed sheets ( e . g ., a bar code 51 , fig2 ). the sheets are moved , as a stack , to a cutting station ( e . g ., a guillotine cutter ), the template is placed on top of the stack of sheets , and the operator enters the template - layout reference number into another terminal to program the guillotine cutter ( or the template - layout reference number is automatically downloaded to the terminal ). the guillotine cutter then cuts the stack of sheets , forming individual stacks of items ( e . g ., business cards , postcards , etc .). in high volume applications , the guillotine cutter can be replaced by automatic cutting or blanking equipment such as is used for cutting labels . while a guillotine cutter is used for most items , e . g ., business cards , postcards , and other flat items ), some items will require other post forming processes . for example , envelopes are formed using standard envelope forming equipment , including a hydraulic die cutter and an envelope folding and gluing machine . because the folding and gluing machines generally require relatively high volumes ( e . g ., 150 , 000 units or more ), it is necessary to accumulate the printed sheets from print runs until the necessary unit volume is reached . in order to keep track of individual print jobs , a marker is placed between each print job and the following print job . this can be accomplished , for example , by using a heavy , brightly colored cardboard sheet as the template , resulting in a brightly colored , sturdy marker at the top of each stack of printed items in a given order . the stacks of items can then be stacked and set aside , or transferred directly to the envelope folding and gluing machine and left there until there are a sufficient number of sheets to operate the machine . other items that require post - processing , e . g ., folders , are processed using appropriate cutting and post - forming techniques , which are well known . after cutting is completed , an operator refers to simple instructions displayed by a terminal , indicating how to package the items . the instructions also indicate whether certain stacks of items should be set aside until a subsequent print run has been completed , e . g ., if a customer has ordered both business cards and letterhead stationery . shipping labels will be printed automatically by a printer attached to one of the browser - based terminals , allowing the operator to easily label the packages for shipping . the labels will generally include a bar code to facilitate shipping using optical - reader based systems , e . g ., as used by ups and fedx carriers . when these carriers are used , the information scanned in by the optical reader can be used by the web server host to track the location of a shipment and , if desired , to inform a customer of the location and / or status of the customer &# 39 ; s order . after an order has been packed and labeled , the operator can simply drop it into a carrier &# 39 ; s bin ( e . g ., a ups bin ) on site . as discussed above , most customers will have prq - paid during ordering , while some corporate customers will have accounts with the web server host , allowing invoicing and later payment . debiting and invoicing of customers is conducted by the backend server upon receipt of a meta file from the printing facility indicating that orders have been successfully shipped . the printing facility and carrier are paid by an automated accounts payable management system after printing and shipping have been successfully completed . referring to fig7 , while a single web server is shown in fig1 for clarity , the system will generally include more than one web server to accommodate a very large volume of users . for example , for volumes of up to around 2 million visits a month , the browser - based processing of the system allows for a small , dedicated print - processing server farm of fewer than 5 servers . the system may be scaled to accommodate many times this amount of visits simply by adding more servers . the servers are arranged in a “ web server farm ”, i . e ., all of the servers used are strictly identical , and the system architecture is implemented so that additional customer requests , that cannot be handled by the existing servers , can be handled by simply adding an extra identical server to the farm . the backend printing servers 28 are also arranged in a farm configuration . in a farm configuration , the load is split between the available servers , so that if more servers are needed either due to overloading of the system or due to a server breaking down the load will continue to be split proportionally among the servers after one is added , removed or replaced . as shown in fig1 , the web server host has supplier relationships with a number of printing firms that are equipped to receive digital data ( layouts ) and informational data ( meta files ) from the system servers . the system includes a program that includes a digital database containing the meta files for each layout . the program fills customer orders by purchasing printing services based on automated real time bidding of commodity costs ( i . e ., paper and ink costs and / or depreciation ). the printing firms bid for near - term printing services based on the capacity utilization of the printer at the time the printing services are needed , by accessing certain parts of the program via the internet . for instance , if a printing firm anticipates a near - term situation of unused capacity , the printing firm will generally price that time period at just above marginal ( commodity ) cost . the program selects the most attractive bid from among the printing firms and transmits the digital data to that firm . the directing and redirecting of capacity can be done up to the very moment of production release . the program may be configured to award a printing contract to the printing firm that is the lowest bidder , or to award the contract based on a group of selection criteria , e . g ., quality , lead time , price , and history . the printing firms may enter into the bidding process through a website operated by the web server host , e . g ., by posting information regarding one - time availability , by posting information regarding long term availability ( e . g ., that a certain time slot is available every day or each week ), or by responding to information regarding layouts that has been posted by the web server host . in some implementations the web site is configured so that a printer will only see information pertaining to layouts that could be printed by that printer ( i . e ., the printer will not see information pertaining to layouts that are in a format that is larger than the format the printer &# 39 ; s press can accommodate .) in some cases , the bidding process will be bypassed entirely . for example , if the web server has a layout that is particularly suitable for a specific printing firm , and the web server knows that the printing firm is available to print the layout , the web server may send the layout and meta files to the printing firm without putting the layout up for bidding by other firms . implementations of the invention involve a division of the characteristics ( and especially the costs ) of the printing product into two major groups : the commodity aspects and costs ; and the informational ( or custom ) aspects and costs . the commodity aspects and costs are those that are deliberately forced to be non - varying among all of the print jobs . these include papers , inks and depreciation . only a relatively small set of different papers may be permitted which reduces the cost of the paper to a bare minimum . only standard process inks may be permitted , which similarly reduces ink costs to a bare minimum . finally , printing equipment costs ( including depreciation expense ) are also in the nature of a commodity across the many jobs that are to be printed . the goal is to reduce these costs to the bare minimum that would be achieved were the presses to be run at fall capacity and with zero setup time . the costs are driven toward this result by using techniques that reduce the setup time to a bare minimum and give the printer equipment owners a medium for easily filling essentially all of their unused capacity . on the informational ( custom ) side are such aspects as definition of content of each print job , price , delivery , and other terms , the ability to reduce capacity underutilization , color definition and verification , variations in quantity , the details of delivery and invoicing , the details of change over and setup , and marketing and sales efforts . on this informational side , too , the goal of the implementations is to drive the costs down ( in theory to near zero ) using information technology , electronic communication , and other techniques . other embodiments are within the scope of the claims . for example , while fixed and variable fields are discussed above in the context of customer - defined templates , in some implementations the web server host may provide templates having this feature as part of the website studio .