Evaluate applications and operating value.
Ask about WMS, QMS, TMS, EDI, profitability, grower management, tariff management, Business Central, devices, or package estimates.
Email Product Questions
Contact AJAX Software
Start with the question, workflow, or result you need.
Contact AJAX Software about product selection, pricing, subscriptions, billing, implementation, support, security, partnerships, FSMA 204 traceability, GS1 labeling, Business Central integration, or any other AJAX OES requirement.
Choose the Best Contact Route
Direct the request to the channel that matches the question.
These direct email routes use the existing AJAX Software addresses and configured channel identifiers.
Resolve checkout or billing questions.
Include the company name and primary-contact email. Never include card numbers, passwords, Stripe secrets, private keys, or access tokens.
Email BillingDescribe the affected workflow and result.
Include the application, environment, document type, expected behaviour, actual behaviour, and safe example references.
Email SupportDiscuss integrations, services, or partnerships.
Explain the organization, intended relationship, geography, product interest, and requested next step.
Email AJAX Software
Send a Message
Use the topic that best matches the request.
The form will use the corresponding email channel configured by the AJAX Platform Administrator.
A Better First Message
Give the receiving team enough context to route the request.
A clear request reduces repeated follow-up and keeps sensitive information out of the initial message.
Name the business need
Describe the outcome: FSMA 204 traceability, GS1 labeling, faster receiving, pallet visibility, quality evidence, simplified production, transportation proof, grower settlement, tariff visibility, or profitability.
Identify the operating context
Include the application, approximate users, devices, locations, monthly volume, Business Central deployment, and relevant workflow.
State the requested next step
Ask for product guidance, pricing clarification, implementation review, support investigation, billing assistance, documentation, or partnership discussion.
Safe Information for the First Message
Share enough to explain the issue.
Company name, contact details, application name, workflow description, non-sensitive document examples, error wording, environment type, expected result, and requested next step.
Information That Should Not Be Submitted
Do not expose the environment.
Passwords, payment-card data, Stripe secrets, OAuth secrets, access tokens, private keys, full connection strings, employee-sensitive data, or unredacted customer and supplier records.
Security and Privacy
Share enough to explain the issue, not enough to expose the environment.