Frequently asked questions

Use https://crm.tradarix.com. The public guide does not require a CRM login.

Complete required security setup, then review Home and your assigned next actions.

No. Password setup and authenticator enrollment are separate steps.

Yes. Close it to view Home; any required security setup still applies.

Your company may require 2FA. Open Activate 2FA and complete enrollment with your own authenticator.

Ordinary verified reset retains MFA. Inactive-user reactivation has a different fresh-enrollment policy.

No. CRM search respects company, role, record and private-participant scope.

Permitted navigation destinations can appear alongside matching records. The guide’s search searches only documentation.

No full-text indexing of raw file contents is promised. Search uses the supported record and document metadata.

Check active filters, pagination, status and access/ownership scope, then search its saved number.

Daily lead actions can be used from a phone browser. Review complex costing/documents carefully on a suitable screen.

A contact is a person; a lead is a sales enquiry/opportunity. One person can be linked to multiple enquiries.

Scheduling is different from accepting a lead and recording real first contact. Complete the applicable acceptance/activity steps.

No. It schedules the next action. Compose and send the actual email separately.

Yes. The Log action form offers each day from 1 through 7, plus the date/time field.

Use the longer-gap reason path when offered. Existing company/lead validation still decides whether it is allowed.

Not necessarily. An exact repeat and a genuine new requirement/cycle can be handled differently. Review the saved result.

No. Qualification follows the saved lead stage/evidence, not just the existence of a draft.

Unused blank rows are skipped. Review validation before saving the filled rows.

It is create-only with duplicate skipping. Use the spreadsheet bulk-update flow for updates.

That mode intentionally updates matched records only; unmatched entries stay uncreated.

They are personal, and Leads and Contacts mappings are separate.

Up to ten per user. Boards still contain only permitted leads.

The quotation start flow requires a valid lead within your permitted scope.

No. Draft saving and send readiness have different rules. Resolve meaningful product, quantity, units, cost and required terms.

Use the explicit zero-cost exception/reason where allowed; do not disguise an incomplete purchase rate as a sample.

Save the draft, reopen/reload it and compare the persisted date with the intended date.

Buyer-facing edits are unsaved. Save and review the intended version before sending.

A bag has no universal weight. Use a supported conversion or matching units and accurate quantities.

An incomplete draft may remain editable, but valid pricing and sending require valid quantity and FX inputs.

No. INR100 cost plus10% is INR110 selling price, giving 9.09% gross margin.

No. Follow the permitted approval process and review the saved quotation.

The revision workflow retains earlier history; verify the intended current version before sharing it.

Use the browser Print action and Save as PDF, then reopen the generated file to check its content.

Supplier/internal-cost permissions can be narrower than buyer access. Use the permitted sourcing or procurement handoff.

No. Reply sync also requires the configured incoming mailbox/provider connection.

For a provider that specifies SMTP465 with SSL/TLS, match that direct TLS setting. Use your provider’s exact port/security instructions.

No. The provider may require an app password or OAuth authorization. Follow its approved connection method.

Up to10 files and20MiB combined in the normal composer. Provider message-size/encoding limits may be smaller.

No. Reattach the files after reopening a draft.

Check verified mailbox, recipient, subject, message, template values and file validation. The composer explains missing requirements.

The default personal signature is automatically appended to new messages and replies. Review the composer before sending.

Up to3 signatures and50 personal templates per user.

No. Image blocking, prefetching and mail-client privacy features affect open events.

Order conversion needs an eligible accepted PI. Review the quotation/PI prerequisites instead of skipping stages.

No. The commercial acceptance and PI/order conversion steps are separate.

Use partial allocations within the remaining quantity and verify the order after each shipment.

The shipment workflow requires a valid eligible order.

Up to20 custom label/value pointers per record, with unique labels and the existing permission checks.

Supplemental pointers do not override commercial quantity/price/tax calculations.

It is optional in the shipment checklist. Commercial Invoice and Packing List retain their required flags.

No. It records receipt/payment information in CRM; it is not a bank transfer instruction.

Only the actual received amount reduces the outstanding balance; reconcile the remaining amount separately.

Review current price, terms, date and availability first. A repeat relationship does not validate old commercial terms.

In the standalone export calculator it applies product-wise to goods, not all added shipment expenses.

Goods-only results are provisional. Confirm the Incoterm, FX and every visible charge including miscellaneous.

Select the supported buyer currency and supply its valid exchange rate. Review INR and buyer-currency values.

No. It uses the supplier’s agreed Incoterm and a separate buyer-cost checklist to avoid double counting.

Check the supplier agreement. Do not re-add seller-paid freight/insurance already included in the quote.

No. Enter actual manual duty/tax amounts. The estimate is not an automatic tariff or tax-credit engine.

Yes. Select feet(ft), inches or centimetres before entering length, width and height.

No. The entered values are interpreted in the selected unit; check/re-enter the dimensions accordingly.

Use the existing inactive user’s approved reactivation flow. It preserves history and issues fresh activation.

Approved reactivation clears old password, sessions and authenticator enrollment; the user sets them up afresh.

No. Access is revoked while identity and commercial history remain. Reassign open work separately.

Inactive users consume no seat. The purchased allowance stays the same and the seat becomes available.

No. Admin hierarchy and self-removal restrictions remain enforced.

Role/team changes revoke old sessions. Sign in again and ask the admin to check the access role separately from the job title.

The admin must assign reporting relationships. A Director role alone does not create reporting members.

Up to5. Main/2nd Admin must complete the required password/authenticator verification to edit them.

Previously selected document bank snapshots remain. Select/update the intended account for the current document and review it.

No. CSS styles a page; authenticated form intake needs the approved server-side connector and mapping.

Use the approved WordPress connector’s private admin settings, never public HTML, CSS or a shared screenshot.

No. Check actual saved status, provider approval and a controlled successful verification.

No. Seats control staff capacity; storage controls file allowance. Check them separately.

The audit/export workflow requires authorised admin access and stays company-scoped.

Respect saved opt-out restrictions and correct consent through the authorised process, not a workaround.

No. Display name/job title and the administrator-assigned access role are different.

Use reports for review, then verify underlying orders, allocations and actual receipts for reconciliation.

Check the same mailbox, server Sent folder and app synchronization settings before resending.

Not if sending succeeded. Repair the mailbox copy/sync problem separately to avoid a duplicate buyer email.

First inspect the result/history or search for the record. Retry only after checking whether the original action succeeded.

No. The coverage map links help to review areas; security, recovery, providers, load and pilot checks need separate current evidence.

Ask the authorised operator/support for current evidence. Never post recovery keys, database dumps or private logs publicly.

No. Role permission and subscription entitlement are independent checks.