# Picqer Fulfilment scoped key: supplier-name mapping

A scoped key cannot read supplier objects; Picqer Fulfilment supplier-name mapping creates suppliers from order names only when enabled.

## Purpose

Choose the right access scope and understand supplier-name mapping with a scoped Picqer Fulfilment key. If you do not know whether supplier-name mapping is enabled, ask Support to confirm it; **unknown supplier** does not identify the mode. Key permissions and Optiply's supplier handling are separate decisions: replacing a scoped key with an admin key is not a safe fix for a missing supplier.

## Prerequisites

Know which Picqer organisation and fulfilment customer the connection should use. Ask the Picqer administrator to identify the key's scope without sharing its value. Review the agreed supplier-handling mode with Support through the [Fulfilment setup guide](/article/connect-picqer-fulfilment).

## Steps

1. Check whether the key is limited to a **Fulfilment customer**. A selected customer means scoped access; an empty selection means global access across the organisation.
2. For a scoped key, expect access only to that customer's allowed products, orders and linked objects. Supplier objects are not among the available scoped endpoints, although purchase orders can carry a supplier name.
3. Check how your Fulfilment connection handles those names. With **supplier-name mapping** enabled, non-empty supplier names can create suppliers in Optiply. A missing name can resolve to **unknown supplier**.
4. If name-derived creation is disabled, ask Support to confirm the existing supplier match or arranged default supplier. Do not treat every unmatched order as an automatic unknown-supplier result.
5. If broader supplier-object imports are required, ask Support to check the connection mode and supported configuration before any key change. A key with more permissions alone does not enable those imports.

## Fields and columns

| Item | Meaning |
| --- | --- |
| Scoped key | Access limited to one fulfilment customer's allowed data. |
| Global/admin key | Account-wide API access; not limited to one fulfilment customer. |
| Purchase-order supplier name | Can supply the name used to create or match an Optiply supplier in Fulfilment mode. It is not a supplier-object export. |
| Default supplier | An arranged Optiply fallback for unresolved incoming supplier matches; not automatically the same as **unknown supplier**. |

## Expected result

You can distinguish the access a key grants from the supplier records your connection is configured to import or resolve. An unknown supplier alone does not demonstrate that authorization failed.

## Limitations

The Fulfilment import route skips direct supplier-object and normal supplier-product imports. Global/admin access does not by itself switch that route to standard-Picqer supplier handling. Supplier creation from an incoming order happens in Optiply; it does not send a supplier object back to Picqer.

## Errors and recovery

If supplier data is missing or unexpected, check key scope and supplier mode together with Support. Do not send the key, broaden its access or swap credentials to test a theory. Keep working credentials in place while any planned change is coordinated.

## Related reading

- [Create a Picqer API key](/article/picqer-setup-and-connection)
- [Picqer data mapping](/article/integrations-data-mappings-public-picqer)
