All Collections
Getting Started
Fulfillment & Shipping Hardware
Fulfillment & Shipping Hardware
Miles Dinsmore avatar
Written by Miles Dinsmore
Updated over a week ago

Throughout the order fulfillment and shipping process, Fulfillment Associates interact with the Seed-to-Sale software through specialized hardware, including the scanner gun, printers, and scales. This article summarizes the hardware a Fulfillment Associates can expect to use as part of the Order Fulfillment and packaging workflow.

Hardware used in this workflow must be integrated with Ample Organics. Contact the Ample Organics Hardware Support team to Add a New Printer, or visit the Settings module to Add a New Scale or Test a Scale's Connection.

Scanner Gun

Model: Zebra MC3200
Purpose: The MC3200 scanner gun hosts the Ample Organics Gun App, and allows you to interact with objects tagged with QR codes–during the order fulfillment workflow, Fulfillment Associates can expect to scan Locations, Bottles, Orders, and Bulk Lots. Several essential functions in the seed-to-sale process are exclusive to the Gun App.

Label Printer

Model: Zebra ZD420
Label Width: 4"
Purpose: Prints GS-128 case labels and shipping labels at the standard 4x6 size.

Visit the ZD420 User Guide.

Letter Size Paper

Model: Unspecified. A licence holder may use their preferred printer model.
Purpose: Prints shipping documents, invoices, fulfillment documents, etc.

Product Label Printer

Model: Epson C7500
Label Width: 1.8" up to 4"
Purpose: The Epson C7500 printer is used in both the packaging and order fulfillment processes to print generic product labels. Please note that this printer only prints one size of labels at a time.

Plant and Product Label Printer

Model: ZT410 (600dpi)
Label Width: Up to 4"
Purpose: The ZT410 printer specializes in printing labels with predefined fields. The 600dpi version prints patient information labels as part of the order fulfillment process.

Visit the ZT400 User Guide.

Learn more about the types of hardware used in the Grow and Packaging workflows.

Did this answer your question?