| 1. fPrint 50 / Lab 50 | 2. fDaemon | 3. Photo Finale REST API |
Recommended Max Volume | 100 orders / day | No limit | No limit |
Operator Interaction Required | Moderate | Very Limited | None |
Requires Windows 7+ machine | Yes | Yes | No |
Order Status Gates Supported | 3 | 10 | 10 |
Supports Individual Status per Order Line Item | No | Yes | Yes |
Supports Individual Tracking Number per Order Line Item | No | Yes | Yes |
Programming Required | No | No | Yes |
Note: it is possible to mix & match the fulfillment methods. For example, you could use fDaemon to download orders but your own integration with our REST API to submit order status updates.
1. USING THE PRINT 50 or LAB 50 WINDOWS APPs
Print 50 and Lab 50 are operator-driven Windows apps that allow you to download orders, print custom invoices & labels, and mark orders are printed or shipped. They are designed to handle the order volume of a typical camera shop and may experience performance issues if your volumes grows beyond a few dozen orders a day. Some basic automatic. Only the three basic order status gates are supported -- order received, order printed, and order shipped. A shipping tracking numbers can be manually entered (only one per order).
2. USING THE fDAEMON WINDOWS APP
Download/run the fDaemon app and it will download any available orders into the C:\fDaemon\Incoming\[fulfiller]\ directory. This path can be configured in the fDaemon.xml file. Each order will be stored in a unique subfolder and will contain all of the rendered pages for the product along with an order metadata xml file.
If you would like fDaemon to be configured to send notifications to you for successful and/or failed orders, please let us know. Notifications can be sent via: Email, HTTP/HTTPS POST, SMS, AWS Lambda, or AWS Simple Queue Service (SQS).
You can post order status changes (printed, shipped, etc.) by dropping text files in the C:\FDaemon\Outgoing\OrderStatus\ directory.
Documentation on the text file format is here: fDaemon
3. USING OUR REST API
Documentation on the HMAC security signature generation required for PF API calls, along with sample code, can be found on this page: Photo Finale API v3 (login required, Photo Finale will provide credentials)
Overview of Integration steps:
- Use the Amazon AWS SDK to poll the SQS queue we provide for order notifications. The order notification message body will contain XML with Order ID and originating Dealer Code: <OrderID>12345678</OrderID><Dealer>1234</Dealer>
- Upon receiving an order notification make a request to the Photo Finale API GetAPMOrderXML method. (GET)
- Use the XML order data to ingest into your system and fulfill the order. Download the rendered pages via the provided URLs in the XML data.
- Submit order status messages back using PF API UpdateOrderStatus method. (PUT)
Additional information on the payload and acceptable values can be found here: Updating Order Status (login required, Photo Finale will provide credentials)