Questions, answered

Click Get started, then use Proto to configure Apparel & Footwear ERP for your business. Set up your workflows, import your data and invite your team.

This system connects customer assortments, style and size-level products, purchased materials, production and finance for apparel and footwear businesses. Each stockkeeping product has its own style, color and size identity where applicable. A seasonal collection groups commercial work without replacing the actual SKU or approved customer quantities.

Yes. Plan a phase around a defined entity and process, with clear ownership of the work that remains in other tools. Reconcile the opening position, integrations and handoffs before launch; retire the old tool for that scope after its outstanding work is accounted for.

The design supports entity-specific functional currencies and accounting calendars. Group reporting needs explicit period mappings, translation policies and ownership methods. A locked consolidation retains those choices and its source amounts so a later change cannot silently rewrite the result.

The accepted offer carries its approved prices, discounts and revision into the order. Invoice allocations retain the source quantities and net amounts so conversion cannot apply a discount again. A contract billing cycle selects an order-led or direct-invoice route and retains that identity to prevent duplicate billing.

Every purchase order needs an eligible approver who did not prepare it. The Buyer or Controller acts within the specified authority. A Controller releases a payment run within their limit and independently of its preparer and included bill approvers. Delegation requires the necessary role and never removes those independence rules.

Access to individual pay, national IDs and employee bank details is restricted. Sales roles do not receive it, and administrative access does not override the restriction. Finance review can use payroll totals and reconciliation evidence; authorized HR and payroll roles retain the detailed access needed for their work.

Compare the configured payroll against the previous provider using a Parallel run for the agreed employees and pay period. It produces comparison evidence without posting journals, creating bank instructions, consuming time or leave, or updating operational year-to-date balances. The payroll owners agree the differences and country-specific responsibilities before release.

Connections are implementation work and depend on the selected provider and country. Confirm the supported formats, identity, acknowledgements and reconciliation behavior during rollout. A payment-file acknowledgement is distinct from settlement, and a configured tax code is not evidence of filing coverage.

Yes, through a planned and reconciled migration. Preserve source identifiers and partial processing history so an already received, shipped, billed or paid amount cannot be processed again. Opening stock, ledger, asset, leave and payroll balances need controlled imports with clear posting boundaries.

Assistants can prepare drafts, propose matches and collect evidence within their assigned access. Required human approvals stay with the accountable role. They cannot bypass document review, payment release, credit controls or sensitive employee access.

There is no per-user fee. The base account and ordinary manual work in the official interface are free. Machine work, retention beyond included allowances and model usage follow the platform rate card; implementation is priced separately. The pricing page explains credit packs, rates and what happens at a zero balance.

Use Proto to propose changes on a branch and review them before release. The process owner should check changes to posting, permissions, payroll or approval rules against existing transactions and the agreed operating policies. Machine work and model usage remain metered.