Configure required service inputs and supplier mappings
Open the service and select its **Fields** tab. Prepare the exact information required to fulfill the service, such as an IMEI, serial, username, selectable option or file. Your field names and mappings must agree with the selected supplier service.
Add or edit a field
1. Choose **Field Type** from the types offered for this service.
2. Set **Name** and, if useful, **Display Label (Optional)**. The display label can be friendly while the field name/mapping remains stable.
3. Add a concise **Description** explaining what the customer should enter.
4. Set **Required** and any supported Min, Max, format or Options controls.
5. Add **Mapping** entries when the supplier expects another field name.
6. Complete the field editor and wait for the save result. Existing product field edits save through the Fields workspace; new products save their fields when the product is added. Test the order form with non-sensitive sample data.
Supplier synchronization
In automatic field-sync mode, connecting or saving a supplier service can set up the order fields that supplier reads. Manual mode keeps staff-defined fields from being changed by the supplier. Review imported requirements before switching modes; custom fields are part of fulfillment, not just visual labels.
**Sync Fields** asks whether to replace all current fields with the latest definitions from the connected supplier. Review that confirmation before continuing. In Auto mode, supplier-connected field names, removal and reordering are protected; switch to Manual only when you intend to maintain those definitions yourself.
The backend validates supported field types and required names. A missing supplier-required field can cause orders to fail even when the catalog price is correct. If an old order lacks a newly required value, reconcile it before resending; adding a field does not invent the customer’s missing information.
**Expected result:** the customer form requests the required values and the supplier receives them through the intended mapping. Keep options clear and do not request passwords or unnecessary personal data in a generic text field.