<\/p>\n
Features<\/h2>\n\n- International Address Validation \u2013 Not Limited to German Addresses.<\/li>\n
- It also recognizes and verifies Packstation and post office branch addresses.<\/li>\n
- Automatic application of valid, unambiguous corrections to street, city, ZIP code, additional line, and state.<\/li>\n
- The order is paused during the review and is then automatically set to a status that you can specify individually for each result\u2014or restored to the status it had previously.<\/li>\n
- Tags are added to the order, and you can view the results in the order overview.<\/li>\n
- A comment on the order stating the results of the review in plain language\u2014which can be disabled if desired. This transparently documents exactly what was corrected.<\/li>\n
- The complete result is also displayed in the task properties\u2014and serves as a way to undo the correction if you want to revert it.<\/li>\n
- Automation Building Blocks \u2192 Flow: You can decide for yourself when to run a check, and thus have a job that has already been checked re-checked as needed\u2014for example, after a manual address correction.<\/li>\n<\/ul>\n
And, of course, all of this is GDPR-compliant.<\/p>\n
<\/p>\n
Getting Started and Prerequisites<\/h2>\n
You need two things:<\/p>\n
\n- An API key from endereco<\/strong>. You can here<\/a> .<\/li>\n
- A set of plugins associated with a client<\/strong>. It usually makes sense to use the default client here. Without this link, no plugin code will run\u2014neither the cron job nor the response to new orders.<\/li>\n<\/ol>\n
Attention<\/strong>: If nothing happens after installation, first check under Plugins \u2192 Plugin Set Overview<\/strong>, whether your plugin set is linked to a tenant. This is the most common cause and isn't mentioned in any error message.<\/p>\nHere's how to set up the plugin<\/strong>:<\/p>\n\n- Install the plugin in your plugin set and redeploy the plugin set.<\/li>\n
- Deploy the plugin set a second time<\/strong>. This is not a precautionary measure: PlentyONE does not perform the plugin's setup steps during the first deployment after installation. Without the second run, the plugin will be missing its table and order properties, and the log will contain error messages about a missing table.<\/li>\n
- Open Plugins \u2192 Plugin Sets<\/strong>, click on the name of your set and then on the plugin within it; here, in the left-hand pane, you'll find the \"Configuration\" option.<\/li>\n
- Wear it in the tab endereco interface<\/strong> Enter your API key and save it.<\/li>\n<\/ol>\n
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/configuration_menu_de.png\")
<\/p>\n
Plugin Configuration<\/h2>\n
\u201eendereco Interface\u201c tab\u201c<\/strong><\/p>\n\n\nSetting<\/td> Standard<\/td> Meaning<\/td><\/tr> Address of the endereco service<\/strong><\/td>https:\/\/endereco-service.de\/rpc\/v1<\/a><\/td> This usually remains unchanged.<\/td><\/tr> API Key<\/strong><\/td>empty<\/td> Your API key from endereco. Required field.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\u201eAddress Validation\u201c tab\u201c<\/strong><\/p>\n\n\n\nSetting<\/td> Standard<\/td> Meaning<\/td><\/tr> Processing<\/strong><\/td>Normal<\/td> To mute the plugin without deactivating it in the plugin set: With \u201eLet it run out\u201c or \u201eStop completely,\u201c the plugin\u2019s flow action remains available but does nothing\u2014flows that use it won\u2019t break as a result, unlike with a complete deactivation. \u201eLet it run out\u201c continues to process the queue, while \u201eStop completely\u201c freezes both immediately.<\/td><\/tr> When should orders be flagged for review?<\/strong><\/td>As soon as an order is received<\/td> Alternatively, you can do this only through a flow that you set up yourself. In either case, the flow action remains available for use.<\/td><\/tr> Apply minor corrections automatically<\/strong><\/td>one<\/td> Enter clear, minor corrections directly into the shipping address\u2014see the note below for what counts as \u201eminor.\u201c.<\/td><\/tr> Record the result as a comment on the order<\/strong><\/td>one<\/td> After each completed exam, write a comment with the result in the order notes.<\/td><\/tr> User ID for comments<\/strong><\/td>1<\/td> The numerical ID of a backend user under which the result comment appears on the order. Without a valid ID, no comment will be posted. A user ID with admin privileges is recommended.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\nNote<\/strong>: Orders received while in \u201eLet Run\u201c or \u201eStop Completely\u201c mode are not automatically flagged for review\u2014not even retroactively when you switch back to \u201eNormal\u201c later. There is no automatic follow-up process that retrieves overlooked orders. If you still want to have such orders reviewed, you must manually flag them yourself using a flow with the action \u201eFlag order for address verification.\u201c.<\/p>\n
\u201eOrder Status\u201c tab\u201c<\/strong><\/p>\n\n\nSetting<\/td> Standard<\/td> Meaning<\/td><\/tr> Status: Waiting for address verification<\/strong><\/td>3.2 (On Hold)<\/td> The status assigned to the job when it is placed in the queue for review.<\/td><\/tr> Target Status: Address Correct<\/strong><\/td>0 (previous status)<\/td> Order status when the address has been confirmed as correct.<\/td><\/tr> Target Status: Minor correction applied<\/strong><\/td>0 (previous status)<\/td> Order status when a minor, verified correction has been automatically applied.<\/td><\/tr> Target Status: Correction suggestion(s) available<\/strong><\/td>0 (previous status)<\/td> Order status when one or more suggested corrections exist but have not been automatically applied\u2014regardless of whether exactly one is too uncertain or multiple possible addresses were found.<\/td><\/tr> Destination status: No address found<\/strong><\/td>0 (previous status)<\/td> Order status when endereco was unable to suggest a correction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\nNote<\/strong>: \u201eStatus: Waiting for Address Verification\u201c does not trigger the verification\u2014the plugin sets this status itself as soon as an order enters the queue, not the other way around. If you want a specific order status to trigger a check, set up a flow for that (see \u201eAdvanced Usage\u201c below).<\/p>\nNote<\/strong>: \u201e0\" means the same thing for every target status: restore the status the job had before the check. If a specified status ID does not (or no longer) exist on your system, the same thing happens automatically\u2014the previous status is restored, and nothing gets stuck.<\/p>\n <\/p>\n
How a job is added to the queue<\/h2>\n
There are two ways for a job to enter the plugin's queue:<\/p>\n
\n- Automatically, when the order is received<\/strong> \u2013 The default scenario, controlled by the setting \u201eWhen should orders be flagged for verification?\u201c (the \u201eAddress Verification\u201c tab). Every new sales order with a shipping address is flagged immediately upon creation.<\/li>\n
- Via a flow, using the \u201eMark for Address Verification\u201c action\u201c<\/strong> \u2013 You decide when the check takes place\u2014for example, only after payment has been received (see \u201eAdvanced Features\u201c below). This action also works for an order that the plugin has already completed\u2014the automatic flag, on the other hand, generally takes effect only once when the order is created.<\/li>\n<\/ul>\n
In both cases, the same thing happens: the plugin queues the job, holds it at the configured start status (default: 3.2 | On Hold), and sets the tag Address validation pending<\/strong>. An order that is already undergoing a review will not be flagged a second time, regardless of what triggered the initial flag.<\/p>\n <\/p>\n
Here's How an Exam Works<\/h2>\n
Once a job has been queued, the verification process continues in exactly the same way\u2014regardless of how it entered the queue:<\/p>\n
\n- A cron job automatically processes the queue every five minutes, retrieving up to 50 queued jobs and checking them one by one.<\/li>\n
- The result is added to the order: tags, properties, a comment (if desired), and\u2014if necessary and permitted\u2014the corrected shipping address. If the address could not be corrected\u2014for example, due to a missing house number\u2014this is also noted in the order notes.<\/li>\n
- The order is assigned the target status configured for this result.<\/li>\n<\/ol>\n
Note<\/strong>: The check does not run immediately upon receipt of the order, but within the next five minutes at the latest. With up to 50 orders per run, the plugin processes up to 600 orders per hour, verifying them without overloading your system\u2014even during periods of high order volume, such as the holiday season, or when a large number of orders are imported all at once.<\/p>\n![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/check_result_tags_de.png\")
<\/p>\n\n\nResult<\/td> Tags on the order<\/td> Shipping Address<\/td> Target Status (Default)<\/td><\/tr> The address was correct<\/td> Address is valid<\/strong><\/td>unchanged<\/td> previous status<\/td><\/tr> Clear correction, accepted<\/td> Address is valid<\/strong> + Address corrected<\/strong><\/td>corrected<\/td> previous status<\/td><\/tr> Correction found, not applied (checkbox not selected, correction not specific enough, or multiple possible addresses found)<\/td> There are issues with the address<\/strong><\/td>unchanged<\/td> previous status<\/td><\/tr> No meaningful correction is possible<\/td> There are issues with the address<\/strong><\/td>unchanged<\/td> previous status<\/td><\/tr> Address validation failed; all attempts have been used up<\/td> Address validation failed<\/strong><\/td>unchanged<\/td> previous status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\nNote<\/strong>: In PlentyONE, tags are always displayed in English regardless of the backend language, even though the plugin also provides German translations\u2014a limitation of PlentyONE itself. This guide therefore refers to the tags in English throughout, just as you would see them in a German-language backend.<\/p>\nNote<\/strong>: Automatic corrections are limited to what can be corrected without supervision: exactly one suggestion and only a minor, clear error\u2014such as a different spelling (\u201eLindenstra\u00dfe 5\u201e to \u201cLindenstr. 5\u201d), a single missing letter, or a single incorrect digit in the ZIP code.<\/p>\n <\/p>\n
The comment on the order<\/h3>\n
If the \u201eRecord result as a comment on the order\u201c setting is enabled, the plugin leaves an internal comment (not visible to the customer) after each completed check, containing the result in plain text, for example:<\/p>\n
\n- \u201eendereco Address Verification: Address is correct.\u201c<\/em><\/li>\n
- \u201eendereco Address Validation: Address automatically corrected.\u201c<\/em><\/li>\n
- \u201eendereco Address Validation: The address could not be corrected automatically.\u201c<\/em> \u2013 with the suggested correction or the reason listed below it, such as \u201eHouse number missing.\u201c<\/li>\n<\/ul>\n
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/check_result_comment_de.png\")
<\/p>\n
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/check_result_comment_2_de.png\")
<\/p>\n
What Remains of the Assignment<\/h3>\n
Under Features<\/strong> You'll find the complete results right next to the order. The address fields are listed in pairs\u2014the value before the check and the suggested value\u2014one directly below the other.<\/p>\n![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/check_result_order_properties_de.png\")
<\/p>\n\n\nProperty<\/td> Content<\/td><\/tr> endereco_process_state<\/td> enqueued<\/code>, checked<\/code> or finished<\/code> \u2013 internal field for the process; no result<\/td><\/tr>endereco_check_outcome<\/td> correct<\/code>, corrected<\/code>, issue<\/code> or failed<\/code><\/td><\/tr>endereco_correction_applied<\/td> whether a correction was entered<\/td><\/tr> endereco_attempts_count<\/td> Number of unsuccessful attempts \u2013 usually remains at 0<\/code><\/td><\/tr>endereco_status_before<\/td> the order status before the review<\/td><\/tr> endereco_address1_original<\/code> \/ _suggestion<\/code><\/td>Previous street and suggested street<\/td><\/tr> endereco_address2_original<\/code> \/ _suggestion<\/code><\/td>Previous house number and proposed house number<\/td><\/tr> endereco_address3_original<\/code> \/ _suggestion<\/code><\/td>Previous and suggested address supplement<\/td><\/tr> endereco_address4_original<\/code> \/ _suggestion<\/code><\/td>\"Free additional field\" previously and suggested<\/td><\/tr> endereco_postal_code_original<\/code> \/ _suggestion<\/code><\/td>Previous ZIP code and suggested ZIP code<\/td><\/tr> endereco_town_original<\/code> \/ _suggestion<\/code><\/td>Previous location and proposed location<\/td><\/tr> endereco_subdivision_original<\/code> \/ _suggestion<\/code><\/td>State\/Region as an ISO code<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\nNote<\/strong>: The fields marked with _original are your fallback: they show the address as it was before the correction. You can restore it at any time, either manually or via a flow. If there was no suggestion (e.g., \u201eno address found\u201c), the _suggestion fields will show \u201cnone\u201d; if there were multiple possible addresses, they will show \u201cmultiple.\u201d.<\/p>\n <\/p>\n
Advanced Use: Other Things You Can Do with Flows<\/h2>\n
The flow integration is intentionally kept open\u2014the \"Mark Order for Address Verification\" action can be combined with any trigger and any other action that Plenty Flow offers. The following two examples are typical use cases, but they represent only a small fraction of what is possible.<\/p>\n
Example: Review only after payment is received<\/h3>\n
Do you only want to review orders that are actually being shipped? Then set the time yourself.<\/p>\n
\n- Position When should orders be flagged for review?<\/strong> on Only through a workflow that you set up yourself<\/em>.<\/li>\n
- Open Automation \u2192 Flow Studio<\/strong>, click on the +<\/strong>-icon and select \"Create New Flow.\".
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_1_de.png\")
<\/li>\n- Give the flow a name, such as Address Verification After Payment Is Received<\/em>.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_2_de.png\")
<\/li>\n- Select as a trigger Event-driven<\/strong>.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_3_de.png\")
<\/li>\n- In the next step, select Event Selection<\/strong> the entry Payment Status<\/strong>. A second field will appear below it, where you can Complete<\/strong> select\u2014that's the \u201efully paid\u201c status.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_4_de.png\")
<\/li>\n- Drag the action from the palette Mark the address verification request<\/strong> on the artboard. The quickest way to find it is through the palette's search field.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_5_de.png\")
<\/li>\n- Save the flow and activate it with Flow Active<\/strong> one.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_6_de.png\")
<\/li>\n<\/ol>\nExample: Have an order that has already been reviewed reviewed again<\/h3>\n
Unlike automatic reservation upon order receipt\u2014which generally processes an order only once\u2014the same flow action can be Mark the address verification request<\/strong> You can also apply this to a job that the plugin has already completed. This is handy if you\u2019ve corrected an address manually and want to review the result afterward. This time, you\u2019ll use a manual trigger that you activate directly on the job\u2014you don\u2019t need to change anything in the \u201eWhen should jobs be flagged for review?\u201c setting.<\/p>\n\n- Open Automation \u2192 Flow Studio<\/strong>, click the + icon and select \"Create New Flow.\".
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_1_step_1_de-1.png\")
<\/li>\n- Give the flow a name, such as Manually Verify the Address Again<\/em>.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_2_de.png\")
<\/li>\n- Select as a trigger Manual<\/strong>.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_3_de.png\")
<\/li>\n- Set to Flow is available in<\/strong> the check marks next to Order UI<\/strong> and Reorder UI<\/strong> \u2013 You can enable both at the same time, depending on where you want to manually trigger the flow later.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_4_de.png\")
<\/li>\n- Drag the action from the palette Mark the address verification request<\/strong> onto the artboard.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_5_de.png\")
<\/li>\n- Save the flow and activate it with Flow Active<\/strong> one.
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_6_de.png\")
<\/li>\n<\/ol>\nFrom now on, you can manually trigger the flow directly from the order.<\/p>\n
<\/p>\n
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_7_de.png\")
<\/p>\n
![\"\"](\"https:\/\/www.endereco.de\/wp-content\/uploads\/2026\/10\/flow_example_2_step_8_de.png\")
<\/p>\n
Billing<\/h2>\n
You are charged for every request that is actually checked\u2014regardless of the response (correct, correctable, ambiguous, or not found\u2014they all count the same). Attempts that fail\u2014due to an incorrect API key or a timeout\u2014cost nothing, even on repeated attempts. A request for which the validation is abandoned after 3 attempts (\u201cAddress validation failed\u201d) is therefore not billed at all.<\/p>\n
And, of course, all of this is GDPR-compliant.<\/p>\n
<\/p>\n
Getting Started and Prerequisites<\/h2>\n
You need two things:<\/p>\n
- \n
- An API key from endereco<\/strong>. You can here<\/a> .<\/li>\n
- A set of plugins associated with a client<\/strong>. It usually makes sense to use the default client here. Without this link, no plugin code will run\u2014neither the cron job nor the response to new orders.<\/li>\n<\/ol>\n
Attention<\/strong>: If nothing happens after installation, first check under Plugins \u2192 Plugin Set Overview<\/strong>, whether your plugin set is linked to a tenant. This is the most common cause and isn't mentioned in any error message.<\/p>\nHere's how to set up the plugin<\/strong>:<\/p>\n
- \n
- Install the plugin in your plugin set and redeploy the plugin set.<\/li>\n
- Deploy the plugin set a second time<\/strong>. This is not a precautionary measure: PlentyONE does not perform the plugin's setup steps during the first deployment after installation. Without the second run, the plugin will be missing its table and order properties, and the log will contain error messages about a missing table.<\/li>\n
- Open Plugins \u2192 Plugin Sets<\/strong>, click on the name of your set and then on the plugin within it; here, in the left-hand pane, you'll find the \"Configuration\" option.<\/li>\n
- Wear it in the tab endereco interface<\/strong> Enter your API key and save it.<\/li>\n<\/ol>\n
<\/p>\nPlugin Configuration<\/h2>\n
\u201eendereco Interface\u201c tab\u201c<\/strong><\/p>\n\n\n
Setting<\/td> Standard<\/td> Meaning<\/td><\/tr> Address of the endereco service<\/strong><\/td> https:\/\/endereco-service.de\/rpc\/v1<\/a><\/td> This usually remains unchanged.<\/td><\/tr> API Key<\/strong><\/td> empty<\/td> Your API key from endereco. Required field.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\u201eAddress Validation\u201c tab\u201c<\/strong><\/p>\n\n\n\nSetting<\/td> Standard<\/td> Meaning<\/td><\/tr> Processing<\/strong><\/td> Normal<\/td> To mute the plugin without deactivating it in the plugin set: With \u201eLet it run out\u201c or \u201eStop completely,\u201c the plugin\u2019s flow action remains available but does nothing\u2014flows that use it won\u2019t break as a result, unlike with a complete deactivation. \u201eLet it run out\u201c continues to process the queue, while \u201eStop completely\u201c freezes both immediately.<\/td><\/tr> When should orders be flagged for review?<\/strong><\/td> As soon as an order is received<\/td> Alternatively, you can do this only through a flow that you set up yourself. In either case, the flow action remains available for use.<\/td><\/tr> Apply minor corrections automatically<\/strong><\/td> one<\/td> Enter clear, minor corrections directly into the shipping address\u2014see the note below for what counts as \u201eminor.\u201c.<\/td><\/tr> Record the result as a comment on the order<\/strong><\/td> one<\/td> After each completed exam, write a comment with the result in the order notes.<\/td><\/tr> User ID for comments<\/strong><\/td> 1<\/td> The numerical ID of a backend user under which the result comment appears on the order. Without a valid ID, no comment will be posted. A user ID with admin privileges is recommended.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n Note<\/strong>: Orders received while in \u201eLet Run\u201c or \u201eStop Completely\u201c mode are not automatically flagged for review\u2014not even retroactively when you switch back to \u201eNormal\u201c later. There is no automatic follow-up process that retrieves overlooked orders. If you still want to have such orders reviewed, you must manually flag them yourself using a flow with the action \u201eFlag order for address verification.\u201c.<\/p>\n
\u201eOrder Status\u201c tab\u201c<\/strong><\/p>\n\n\nSetting<\/td> Standard<\/td> Meaning<\/td><\/tr> Status: Waiting for address verification<\/strong><\/td> 3.2 (On Hold)<\/td> The status assigned to the job when it is placed in the queue for review.<\/td><\/tr> Target Status: Address Correct<\/strong><\/td> 0 (previous status)<\/td> Order status when the address has been confirmed as correct.<\/td><\/tr> Target Status: Minor correction applied<\/strong><\/td> 0 (previous status)<\/td> Order status when a minor, verified correction has been automatically applied.<\/td><\/tr> Target Status: Correction suggestion(s) available<\/strong><\/td> 0 (previous status)<\/td> Order status when one or more suggested corrections exist but have not been automatically applied\u2014regardless of whether exactly one is too uncertain or multiple possible addresses were found.<\/td><\/tr> Destination status: No address found<\/strong><\/td> 0 (previous status)<\/td> Order status when endereco was unable to suggest a correction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n Note<\/strong>: \u201eStatus: Waiting for Address Verification\u201c does not trigger the verification\u2014the plugin sets this status itself as soon as an order enters the queue, not the other way around. If you want a specific order status to trigger a check, set up a flow for that (see \u201eAdvanced Usage\u201c below).<\/p>\n
Note<\/strong>: \u201e0\" means the same thing for every target status: restore the status the job had before the check. If a specified status ID does not (or no longer) exist on your system, the same thing happens automatically\u2014the previous status is restored, and nothing gets stuck.<\/p>\n
<\/p>\n
How a job is added to the queue<\/h2>\n
There are two ways for a job to enter the plugin's queue:<\/p>\n
- \n
- Automatically, when the order is received<\/strong> \u2013 The default scenario, controlled by the setting \u201eWhen should orders be flagged for verification?\u201c (the \u201eAddress Verification\u201c tab). Every new sales order with a shipping address is flagged immediately upon creation.<\/li>\n
- Via a flow, using the \u201eMark for Address Verification\u201c action\u201c<\/strong> \u2013 You decide when the check takes place\u2014for example, only after payment has been received (see \u201eAdvanced Features\u201c below). This action also works for an order that the plugin has already completed\u2014the automatic flag, on the other hand, generally takes effect only once when the order is created.<\/li>\n<\/ul>\n
In both cases, the same thing happens: the plugin queues the job, holds it at the configured start status (default: 3.2 | On Hold), and sets the tag Address validation pending<\/strong>. An order that is already undergoing a review will not be flagged a second time, regardless of what triggered the initial flag.<\/p>\n
<\/p>\n
Here's How an Exam Works<\/h2>\n
Once a job has been queued, the verification process continues in exactly the same way\u2014regardless of how it entered the queue:<\/p>\n
- \n
- A cron job automatically processes the queue every five minutes, retrieving up to 50 queued jobs and checking them one by one.<\/li>\n
- The result is added to the order: tags, properties, a comment (if desired), and\u2014if necessary and permitted\u2014the corrected shipping address. If the address could not be corrected\u2014for example, due to a missing house number\u2014this is also noted in the order notes.<\/li>\n
- The order is assigned the target status configured for this result.<\/li>\n<\/ol>\n
Note<\/strong>: The check does not run immediately upon receipt of the order, but within the next five minutes at the latest. With up to 50 orders per run, the plugin processes up to 600 orders per hour, verifying them without overloading your system\u2014even during periods of high order volume, such as the holiday season, or when a large number of orders are imported all at once.<\/p>\n<\/p>\n\n\nResult<\/td> Tags on the order<\/td> Shipping Address<\/td> Target Status (Default)<\/td><\/tr> The address was correct<\/td> Address is valid<\/strong><\/td> unchanged<\/td> previous status<\/td><\/tr> Clear correction, accepted<\/td> Address is valid<\/strong> + Address corrected<\/strong><\/td> corrected<\/td> previous status<\/td><\/tr> Correction found, not applied (checkbox not selected, correction not specific enough, or multiple possible addresses found)<\/td> There are issues with the address<\/strong><\/td> unchanged<\/td> previous status<\/td><\/tr> No meaningful correction is possible<\/td> There are issues with the address<\/strong><\/td> unchanged<\/td> previous status<\/td><\/tr> Address validation failed; all attempts have been used up<\/td> Address validation failed<\/strong><\/td> unchanged<\/td> previous status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n Note<\/strong>: In PlentyONE, tags are always displayed in English regardless of the backend language, even though the plugin also provides German translations\u2014a limitation of PlentyONE itself. This guide therefore refers to the tags in English throughout, just as you would see them in a German-language backend.<\/p>\n
Note<\/strong>: Automatic corrections are limited to what can be corrected without supervision: exactly one suggestion and only a minor, clear error\u2014such as a different spelling (\u201eLindenstra\u00dfe 5\u201e to \u201cLindenstr. 5\u201d), a single missing letter, or a single incorrect digit in the ZIP code.<\/p>\n
<\/p>\n
The comment on the order<\/h3>\n
If the \u201eRecord result as a comment on the order\u201c setting is enabled, the plugin leaves an internal comment (not visible to the customer) after each completed check, containing the result in plain text, for example:<\/p>\n
- \n
- \u201eendereco Address Verification: Address is correct.\u201c<\/em><\/li>\n
- \u201eendereco Address Validation: Address automatically corrected.\u201c<\/em><\/li>\n
- \u201eendereco Address Validation: The address could not be corrected automatically.\u201c<\/em> \u2013 with the suggested correction or the reason listed below it, such as \u201eHouse number missing.\u201c<\/li>\n<\/ul>\n
<\/p>\n<\/p>\nWhat Remains of the Assignment<\/h3>\n
Under Features<\/strong> You'll find the complete results right next to the order. The address fields are listed in pairs\u2014the value before the check and the suggested value\u2014one directly below the other.<\/p>\n
<\/p>\n\n\nProperty<\/td> Content<\/td><\/tr> endereco_process_state<\/td> enqueued<\/code>,checked<\/code> orfinished<\/code> \u2013 internal field for the process; no result<\/td><\/tr>endereco_check_outcome<\/td> correct<\/code>,corrected<\/code>,issue<\/code> orfailed<\/code><\/td><\/tr>endereco_correction_applied<\/td> whether a correction was entered<\/td><\/tr> endereco_attempts_count<\/td> Number of unsuccessful attempts \u2013 usually remains at 0<\/code><\/td><\/tr>endereco_status_before<\/td> the order status before the review<\/td><\/tr> endereco_address1_original<\/code> \/_suggestion<\/code><\/td>Previous street and suggested street<\/td><\/tr> endereco_address2_original<\/code> \/_suggestion<\/code><\/td>Previous house number and proposed house number<\/td><\/tr> endereco_address3_original<\/code> \/_suggestion<\/code><\/td>Previous and suggested address supplement<\/td><\/tr> endereco_address4_original<\/code> \/_suggestion<\/code><\/td>\"Free additional field\" previously and suggested<\/td><\/tr> endereco_postal_code_original<\/code> \/_suggestion<\/code><\/td>Previous ZIP code and suggested ZIP code<\/td><\/tr> endereco_town_original<\/code> \/_suggestion<\/code><\/td>Previous location and proposed location<\/td><\/tr> endereco_subdivision_original<\/code> \/_suggestion<\/code><\/td>State\/Region as an ISO code<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n Note<\/strong>: The fields marked with _original are your fallback: they show the address as it was before the correction. You can restore it at any time, either manually or via a flow. If there was no suggestion (e.g., \u201eno address found\u201c), the _suggestion fields will show \u201cnone\u201d; if there were multiple possible addresses, they will show \u201cmultiple.\u201d.<\/p>\n
<\/p>\n
Advanced Use: Other Things You Can Do with Flows<\/h2>\n
The flow integration is intentionally kept open\u2014the \"Mark Order for Address Verification\" action can be combined with any trigger and any other action that Plenty Flow offers. The following two examples are typical use cases, but they represent only a small fraction of what is possible.<\/p>\n
Example: Review only after payment is received<\/h3>\n
Do you only want to review orders that are actually being shipped? Then set the time yourself.<\/p>\n
- \n
- Position When should orders be flagged for review?<\/strong> on Only through a workflow that you set up yourself<\/em>.<\/li>\n
- Open Automation \u2192 Flow Studio<\/strong>, click on the +<\/strong>-icon and select \"Create New Flow.\".
<\/li>\n- Give the flow a name, such as Address Verification After Payment Is Received<\/em>.
<\/li>\n- Select as a trigger Event-driven<\/strong>.
<\/li>\n- In the next step, select Event Selection<\/strong> the entry Payment Status<\/strong>. A second field will appear below it, where you can Complete<\/strong> select\u2014that's the \u201efully paid\u201c status.
<\/li>\n- Drag the action from the palette Mark the address verification request<\/strong> on the artboard. The quickest way to find it is through the palette's search field.
<\/li>\n- Save the flow and activate it with Flow Active<\/strong> one.
<\/li>\n<\/ol>\nExample: Have an order that has already been reviewed reviewed again<\/h3>\n
Unlike automatic reservation upon order receipt\u2014which generally processes an order only once\u2014the same flow action can be Mark the address verification request<\/strong> You can also apply this to a job that the plugin has already completed. This is handy if you\u2019ve corrected an address manually and want to review the result afterward. This time, you\u2019ll use a manual trigger that you activate directly on the job\u2014you don\u2019t need to change anything in the \u201eWhen should jobs be flagged for review?\u201c setting.<\/p>\n
- \n
- Open Automation \u2192 Flow Studio<\/strong>, click the + icon and select \"Create New Flow.\".<\/li>\n
- Give the flow a name, such as Manually Verify the Address Again<\/em>.
<\/li>\n- Select as a trigger Manual<\/strong>.
<\/li>\n- Set to Flow is available in<\/strong> the check marks next to Order UI<\/strong> and Reorder UI<\/strong> \u2013 You can enable both at the same time, depending on where you want to manually trigger the flow later.
<\/li>\n- Drag the action from the palette Mark the address verification request<\/strong> onto the artboard.
<\/li>\n- Save the flow and activate it with Flow Active<\/strong> one.
<\/li>\n<\/ol>\nFrom now on, you can manually trigger the flow directly from the order.<\/p>\n
<\/p>\n
<\/p>\n<\/p>\nBilling<\/h2>\n
You are charged for every request that is actually checked\u2014regardless of the response (correct, correctable, ambiguous, or not found\u2014they all count the same). Attempts that fail\u2014due to an incorrect API key or a timeout\u2014cost nothing, even on repeated attempts. A request for which the validation is abandoned after 3 attempts (\u201cAddress validation failed\u201d) is therefore not billed at all.<\/p>\n
- Give the flow a name, such as Manually Verify the Address Again<\/em>.
- Open Automation \u2192 Flow Studio<\/strong>, click on the +<\/strong>-icon and select \"Create New Flow.\".
- \u201eendereco Address Validation: Address automatically corrected.\u201c<\/em><\/li>\n
- \u201eendereco Address Verification: Address is correct.\u201c<\/em><\/li>\n
- Via a flow, using the \u201eMark for Address Verification\u201c action\u201c<\/strong> \u2013 You decide when the check takes place\u2014for example, only after payment has been received (see \u201eAdvanced Features\u201c below). This action also works for an order that the plugin has already completed\u2014the automatic flag, on the other hand, generally takes effect only once when the order is created.<\/li>\n<\/ul>\n
- Open Plugins \u2192 Plugin Sets<\/strong>, click on the name of your set and then on the plugin within it; here, in the left-hand pane, you'll find the \"Configuration\" option.<\/li>\n
- A set of plugins associated with a client<\/strong>. It usually makes sense to use the default client here. Without this link, no plugin code will run\u2014neither the cron job nor the response to new orders.<\/li>\n<\/ol>\n