timastra
← All guides

Timastra Inventory

Choose inventory capacity from your workflow

Timastra ·

Count locations, products and team access before comparing inventory software plans.

An inventory plan should fit the operation that will use it. A low headline price is useful only if the workspace can cover the required locations, products and authorized team members. Count those requirements before comparing plans.

List active warehouse locations and the people who need access. Review the product catalogue and distinguish current products from records that are genuinely no longer used. Do not remove needed history merely to make a capacity count look smaller.

Then identify the workflow requirements. Does the team need purchasing and fulfillment records, external connections, API access or scheduled reports? Mark each as required now, useful later or unnecessary. Verify plan-specific availability instead of assuming all plans include every feature.

In a fictional business, two warehouses and five regular users create a different plan question from one warehouse and two users. The product count and integration requirements still matter. The appropriate choice depends on the actual limits and workflow, not that example alone.

Allow for foreseeable changes without treating growth as certain. Compare your requirements with the current plan page and order summary. Ask through the available enquiry path when a capacity allowance is unclear; unsupported add-ons should not be assumed available.

Timastra Inventory offers plans with different warehouse, product and user capacities. API access and webhooks are described on Growth and Scale, and scheduled reports on Scale. Explore the current product page for plan scope. Hardware, inventory purchases, postage and third-party subscriptions are separate costs.