Customer Export Profile
The Customer Export Profile synchronizes customer data from Magento to PlentyONE, creating contacts and updating customer information in your ERP system.
Overview
Profile Type ID: plenty_customer_export
Direction: Magento → PlentyONE
Purpose: Export customer accounts, addresses, and contact details to PlentyONE
What Gets Exported
- Customer accounts as PlentyONE contacts
- Customer addresses (billing and shipping)
- Customer groups/classifications
- Customer metadata and custom attributes
Key Use Cases
- Order Processing: Export Magento customers to PlentyONE for order fulfillment
- CRM Integration: Sync customer data for marketing and support
- Automated Export: Trigger export when customer creates account
- Guest Checkout: Create PlentyONE contacts for guest orders
Configuration Highlights
The Customer Export profile shares most configuration with Customer Import, with these key differences:
Customer Configuration Differences
Export Direction
All mappings work in reverse (Magento → PlentyONE):
- Group Mapping: Magento group → PlentyONE class
- Gender Mapping: Magento prefix → PlentyONE gender
- Address Mapping: Magento fields → PlentyONE fields
Default Group (PlentyONE)
Field: default_group
Type: Select
Scope: Global
Select the default PlentyONE customer class for new contacts.
Source: Uses PlentyONE customer classes (not Magento groups)
Example:
Default Group: Standard Customer (PlentyONE)
Behavior: When exporting a new customer without
group mapping, assigns "Standard Customer" class
in PlentyONE
Store Filter (Export Direction)
Field: is_active_store_filter
Type: Checkbox
Default: No
Restricts customer export by store view.
Tooltip: "Restricts customer export by mapped stores. Customers created in stores that are not included in the mapping will be excluded from export."
Use Case:
Scenario: Multi-store with B2B and B2C separation
Store Mapping:
- B2C Store → PlentyONE Client Retail
- B2B Store → PlentyONE Client Wholesale
Enable Store Filter: Yes
Result: B2C customers only export to Retail client
B2B customers only export to Wholesale client
Auto-Export Configuration
Customer Export supports automatic export when customers are created or register.
Manual Queue Management
Unlike Category Export's event observers, Customer Export uses queue-based processing:
Workflow:
- Customer registers/is created in Magento
- Customer is added to export queue (if configured)
- Scheduled profile execution processes queue
- Customer exported to PlentyONE
Queue Commands:
# View export queue
bin/magento softcommerce:plenty:customer:queue --list
# Add customer to queue
bin/magento softcommerce:plenty:customer:queue --add --entity-id=123
# Clear queue
bin/magento softcommerce:plenty:customer:queue --clear
# Process queue manually
bin/magento softcommerce:plenty:customer:export --profile-id=4 --queue
Group Mapping Strategy
B2B vs B2C Separation
Magento Groups:
- General (B2C retail)
- Wholesale (B2B)
- VIP (Premium)
PlentyONE Classes:
- Standard Customer
- Business Customer
- Premium Customer
Mapping Example:
| Magento Group | PlentyONE Class | Pricing Tier |
|---|---|---|
| General | Standard Customer | Retail |
| Wholesale | Business Customer | Wholesale |
| VIP | Premium Customer | VIP |
Multi-Store Group Strategy
Scenario: Regional pricing differences
| Store | Magento Group | PlentyONE Class |
|---|---|---|
| US Store | General | US Retail |
| EU Store | General | EU Retail |
| UK Store | General | UK Retail |
Configuration:
- Use store filter: Yes
- Different group mappings per store view
- Separate referrers per region
Address Field Mapping Best Practices
Required Fields
Always map these essential fields:
| Magento Field | PlentyONE Field | Required |
|---|---|---|
| firstname | firstName | Yes |
| lastname | lastName | Yes |
| street | street | Yes |
| city | town | Yes |
| postcode | postalCode | Yes |
| country_id | country | Yes |
Optional But Recommended
| Magento Field | PlentyONE Field | Use Case |
|---|---|---|
| company | companyName | B2B customers |
| telephone | phone | Contact info |
| region | state | US/CA addresses |
| vat_id | vatNumber | EU B2B |
Custom Fields
Example: Export loyalty program ID
- Create Magento Customer Attribute:
loyalty_id - Create PlentyONE Custom Field:
Custom_LoyaltyID - Add Address Field Mapping:
- Magento: loyalty_id
- PlentyONE: Custom_LoyaltyID
CLI Commands
# Export all customers
bin/magento softcommerce:plenty:customer:export --profile-id=4
# Export specific customers
bin/magento softcommerce:plenty:customer:export --profile-id=4 --entity-ids=100,101
# Export new customers only
bin/magento softcommerce:plenty:customer:export --profile-id=4 --new-only
# Export with store filter
bin/magento softcommerce:plenty:customer:export --profile-id=4 --store-id=1
# Process export queue
bin/magento softcommerce:plenty:customer:export --profile-id=4 --queue
Troubleshooting
Customer Not Exported
Solutions:
- Check store filter settings
- Verify customer belongs to mapped store
- Review export queue for stuck items
- Check PlentyONE API credentials
Wrong Customer Class in PlentyONE
Solutions:
- Verify group mapping (Magento → PlentyONE direction)
- Check default group assignment
- Review customer group in Magento
- Ensure mapping covers all groups
Missing Address Data
Solutions:
- Verify address field mappings are complete
- Check customer has addresses in Magento
- Ensure address is marked as default
- Review address validation requirements
Best Practices
Initial Export
- Test with Small Set: Export 5-10 customers first
- Verify Data Quality: Check exported contacts in PlentyONE
- Validate Mappings: Confirm groups and addresses are correct
- Full Export: Process all customers after validation
Ongoing Synchronization
- Queue-Based: Use queue for automatic exports
- Schedule Frequency: Every 15-30 minutes for near real-time
- Monitor Queue: Check for stuck or failed exports
- Error Handling: Enable history to track issues
Multi-Store Exports
- Separate Referrers: Use different referrer per store/region
- Store Filter: Enable for regional customer separation
- Group Strategy: Plan group structure for multi-store needs
- Test Per Store: Validate exports for each store view