Fair Usage Policy
How PackageX measures platform usage, annual allowances and rate limits.
Questions about this document
support@packagex.ioPackageX, Inc. · 500 7th Avenue, 8th Floor, New York, NY 10018
1. Usage Philosophy
PackageX measures usage primarily based on completed operational workflow executions and cloud-processing events which impact server and database capacity (“Resources”), rather than local scans, cached validations, offline mobile actions, or user-interface navigation. The intent of this Policy is to align platform consumption with meaningful operational outcomes while supporting commercially reasonable implementation practices.
This document outlines how PackageX measures platform usage and what counts toward Annual Allowance. It is designed to give you a clear, straightforward understanding of your consumption so you can plan effectively and avoid unexpected interruptions.
2. Definitions
"Annual Allowance" means the total number of Resources included per Workflow per annual period, as set out in the "Annual Allowance Structure" section below.
"Order Form" means the ordering document executed between you and PackageX that specifies the Workflows, pricing, and other commercial terms applicable to your use of the Platform.
"Resources": A Resource may include one or more creation or consumption of below resources as part of Services which impact server and database capacity including but not limited to as defined further in Schedule 1.
"Workflow" means a distinct operational configuration provisioned under your PackageX account, as specified in your Order Form or Master Services Agreement.
"Request" A Request is a single message, command, or data transmission sent from a client to a server to perform an action or retrieve information.
"Workflow" means a distinct operational configuration provisioned under your PackageX account, as specified in your Order Form or Master Services Agreement.
3. Annual Allowance Structure
The annual allowance is 250,000 Resources per Workflow per Contract Year (the “Annual Allowance”). All allowances reset to zero at the anniversary of your contract start date. The Allowance can be pooled for all Workflows subscribed to if contemplated in the Order signed between PackageX and the Customer.
4. Usage Reviews
PackageX and Customer shall review actual usage metrics periodically (at least twice each year) during any testing and in production operations. If actual consumption materially exceeds directional estimates, the parties will work in good faith to optimize workflow architecture; reduce unnecessary activity; and/or agree on revised commercial usage thresholds or commercial pricing where appropriate.
5. Usage Notifications and Governance
PackageX will provide proactive notice at 75%, 90%, and 100% of the Annual Allowance. Except in cases of abusive or fraudulent usage, PackageX will not suspend operational workflows solely due to overage consumption without commercially reasonable prior notice and an opportunity to discuss mitigation or revised usage allocations.
6. Overage and Additional Usage
Before imposing any overage charges resulting from usage materially exceeding Annual Allowance, PackageX shall first:
- a) provide commercially reasonable advance notice;
- b) identify the primary usage drivers;
- c) recommend commercially reasonable optimization measures; and
- d) provide Customer an opportunity to mitigate excessive consumption.
7. Rate Limits
In addition to your Annual Allowance, the Services are subject to a rate limit of 500 Requests / Minute and as may be published in the PackageX API Documentation or otherwise communicated to the Customer. Rate limits are applied to protect platform performance and stability for all customers. Calls that exceed the applicable rate limit will receive an HTTP 429 (Too Many Requests) response and should be retried after the interval specified in the response header.
8. Prohibited Use and Anti-Abuse
You agree not to circumvent or attempt to circumvent the usage measurement mechanisms described in this Policy, including by disguising write operations as read-only requests, generating automated or bot-driven traffic intended to inflate or manipulate usage counts, or using the Platform in any manner that degrades performance for other customers.
PackageX reserves the right to throttle or suspend access to any Workflow where it reasonably determines that usage patterns are abusive, fraudulent, or materially inconsistent with normal business operations. PackageX will provide you with reasonable notice before taking any such action, except where immediate action is necessary to protect platform integrity. Ordinary operational variance, exception-heavy workflows, retries due to connectivity limitations, OS&D handling, relabeling, recounts, attachment-heavy workflows, and standard warehouse operational rework shall not constitute abusive or fraudulent usage.
9. Policy Updates
PackageX may update this Fair Usage Policy from time to time. Material changes to any counting methodology, workflow metering logic, or allowance calculation methodology shall not apply retroactively and shall require at least thirty (30) days prior written notice to Customer.
Schedule 1
Resources
Definitions (not all definitions may apply to your License or use case):
| Users | Manages user accounts, permissions, user role assignments, and notification preferences. |
| Contacts | A person or business entity with one or more contact channels (emails, phones) and addresses (primary, work, home, etc.). Used as senders/recipients on shipments, fulfillments, and manifests, and as the assignee on assets. |
| Groups | A named collection of a single resource type (contacts or locations) used for bulk operations and organizing related parties. |
| Items | A product definition (the catalog SKU), not a physical unit. Holds the GTIN, dimensions, weight, packaging, attributes, and inventory levels across locations and layouts. |
| Assets | An individual, uniquely identified physical unit tracked by serial number and barcode. Each asset is an instance of an Item and carries its own status (e.g., in_storage, in_transit), location/layout placement, value, warranty, and maintenance/disposal records. |
| Fulfillments | An outbound warehouse order to pick, pack, and ship items from a location to a recipient. Contains the line items and parcels, sender/recipient details, a packing slip, and pick/pack/ship workflow steps. Links one-to-one to a Shipment. |
| Manifests | The inbound warehouse order: a record of goods received from a vendor/sender. Lists of incoming articles and parcels with tracking and moves through requested, arrived, and processed. |
| Shipments | A single parcel movement (outbound or inbound) bound to a carrier provider, with a purchased rate, tracking number, label, customs info, and delivery status. Linked to one fulfillment, its parcels, a container, and a tracker; supports parent/child legs for multi-leg moves. |
| Trackers | A tracking record following a package’s journey independent of who bought the label. Holds status, estimated delivery, chained multi-leg shipments, and sender/destination contacts; can spawn internal or destination shipments and auto close on delivery. |
| Containers | A grouping of multiple shipments moving together (e.g., a pallet or LTL container) under one unified tracking number and status, tied to a location/layout |
| Parcels | A physical box/package with its own dimensions, weight, contents, label, and status. Belongs to either a fulfillment or a manifest and carries shipping form URLs (CN22, commercial invoice, etc.) and special-handling tags. |
| Documents | A versioned file artifact (invoice, label, manifest PDF, etc.). Attaches to resources such as assets, shipments, items, manifests, and fulfillments. |
| Lots | Manages batches of inventory, such as production lots, for traceability and tracking. |
| Audits | An individual task commonly referred to as ‘cycle counting’ that is generated and completed via a lifecycle of counting and updating inventory items. Audit tasks are capped and can only contain a limited finite number of levels of inventory to count. Check API docs for current limits. |
| Reports | A report is a single physical PDF operation that combines and builds a pdf and can be shared externally. Every refresh to pull new data requires building a new PDF which constitutes a new report. |
Please refer to our documentation for any updates on the Resources. https://docs.packagex.io/