| ( ! ) Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>complianz-gdpr</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/ecommerceaggregators.com/public_html/wp-includes/functions.php on line 6114 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.0001 | 361072 | require_once( '/home/ecommerceaggregators.com/public_html/wp-load.php' ) | .../wp-blog-header.php:13 |
| 4 | 0.0002 | 361400 | require_once( '/home/ecommerceaggregators.com/public_html/wp-config.php' ) | .../wp-load.php:50 |
| 5 | 0.0002 | 362800 | require_once( '/home/ecommerceaggregators.com/public_html/wp-settings.php' ) | .../wp-config.php:112 |
| 6 | 0.2323 | 10869336 | do_action( ) | .../wp-settings.php:559 |
| 7 | 0.2323 | 10869712 | WP_Hook->do_action( ) | .../plugin.php:517 |
| 8 | 0.2323 | 10869712 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.2375 | 11092760 | {closure:/home/ecommerceaggregators.com/public_html/wp-content/plugins/complianz-gdpr/complianz-gpdr.php:217-219}( ) | .../class-wp-hook.php:324 |
| 10 | 0.2375 | 11092760 | COMPLIANZ::get_instance( ) | .../complianz-gpdr.php:218 |
| 11 | 0.2375 | 11092800 | COMPLIANZ->__construct( ) | .../complianz-gpdr.php:157 |
| 12 | 0.2393 | 11267888 | cmplz_config->__construct( ) | .../complianz-gpdr.php:89 |
| 13 | 0.2393 | 11267912 | __( ) | .../class-config.php:264 |
| 14 | 0.2393 | 11267912 | translate( ) | .../l10n.php:306 |
| 15 | 0.2393 | 11267912 | get_translations_for_domain( ) | .../l10n.php:194 |
| 16 | 0.2393 | 11267912 | _load_textdomain_just_in_time( ) | .../l10n.php:1408 |
| 17 | 0.2394 | 11269400 | _doing_it_wrong( ) | .../l10n.php:1378 |
| 18 | 0.2394 | 11271512 | wp_trigger_error( ) | .../functions.php:6054 |
| 19 | 0.2398 | 11273000 | trigger_error ( ) | .../functions.php:6114 |
| ( ! ) Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>updraftplus</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/ecommerceaggregators.com/public_html/wp-includes/functions.php on line 6114 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.0001 | 361072 | require_once( '/home/ecommerceaggregators.com/public_html/wp-load.php' ) | .../wp-blog-header.php:13 |
| 4 | 0.0002 | 361400 | require_once( '/home/ecommerceaggregators.com/public_html/wp-config.php' ) | .../wp-load.php:50 |
| 5 | 0.0002 | 362800 | require_once( '/home/ecommerceaggregators.com/public_html/wp-settings.php' ) | .../wp-config.php:112 |
| 6 | 0.2323 | 10869336 | do_action( ) | .../wp-settings.php:559 |
| 7 | 0.2323 | 10869712 | WP_Hook->do_action( ) | .../plugin.php:517 |
| 8 | 0.2323 | 10869712 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.2606 | 11874480 | UpdraftPlus->plugins_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.2607 | 11885320 | updraft_try_include_file( ) | .../class-updraftplus.php:751 |
| 11 | 0.2608 | 11886072 | include_once( '/home/ecommerceaggregators.com/public_html/wp-content/plugins/updraftplus/central/factory.php' ) | .../updraftplus.php:103 |
| 12 | 0.2609 | 11886128 | UpdraftCentral_Factory::create_host( ) | .../factory.php:77 |
| 13 | 0.2613 | 11890680 | UpdraftPlus_Host::instance( ) | .../factory.php:67 |
| 14 | 0.2613 | 11890840 | UpdraftPlus_Host->__construct( ) | .../updraftplus.php:29 |
| 15 | 0.2613 | 11895096 | UpdraftPlus_Host->maybe_initialize_required_objects( ) | .../updraftplus.php:43 |
| 16 | 0.2614 | 11895384 | include_once( '/home/ecommerceaggregators.com/public_html/wp-content/plugins/updraftplus/central/translations-central.php' ) | .../updraftplus.php:273 |
| 17 | 0.2614 | 11895384 | __( ) | .../translations-central.php:9 |
| 18 | 0.2614 | 11895384 | translate( ) | .../l10n.php:306 |
| 19 | 0.2614 | 11895384 | get_translations_for_domain( ) | .../l10n.php:194 |
| 20 | 0.2614 | 11895384 | _load_textdomain_just_in_time( ) | .../l10n.php:1408 |
| 21 | 0.2615 | 11896496 | _doing_it_wrong( ) | .../l10n.php:1378 |
| 22 | 0.2616 | 11897328 | wp_trigger_error( ) | .../functions.php:6054 |
| 23 | 0.2619 | 11897968 | trigger_error ( ) | .../functions.php:6114 |
| ( ! ) Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>wpforms-lite</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/ecommerceaggregators.com/public_html/wp-includes/functions.php on line 6114 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.0001 | 361072 | require_once( '/home/ecommerceaggregators.com/public_html/wp-load.php' ) | .../wp-blog-header.php:13 |
| 4 | 0.0002 | 361400 | require_once( '/home/ecommerceaggregators.com/public_html/wp-config.php' ) | .../wp-load.php:50 |
| 5 | 0.0002 | 362800 | require_once( '/home/ecommerceaggregators.com/public_html/wp-settings.php' ) | .../wp-config.php:112 |
| 6 | 0.2323 | 10869336 | do_action( ) | .../wp-settings.php:559 |
| 7 | 0.2323 | 10869712 | WP_Hook->do_action( ) | .../plugin.php:517 |
| 8 | 0.2323 | 10869712 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.2812 | 12567360 | WPForms\WPForms->objects( ) | .../class-wp-hook.php:324 |
| 10 | 0.2814 | 12604760 | do_action( ) | .../WPForms.php:261 |
| 11 | 0.2814 | 12605136 | WP_Hook->do_action( ) | .../plugin.php:517 |
| 12 | 0.2814 | 12605136 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 13 | 0.2819 | 12625720 | WPForms\WPForms->WPForms\{closure:/home/ecommerceaggregators.com/public_html/wp-content/plugins/wpforms-lite/src/WPForms.php:296-306}( ) | .../class-wp-hook.php:324 |
| 14 | 0.2819 | 12626080 | WPForms\Forms\Locator->init( ) | .../WPForms.php:304 |
| 15 | 0.2823 | 12629312 | __( ) | .../Locator.php:175 |
| 16 | 0.2823 | 12629312 | translate( ) | .../l10n.php:306 |
| 17 | 0.2823 | 12629312 | get_translations_for_domain( ) | .../l10n.php:194 |
| 18 | 0.2823 | 12629312 | _load_textdomain_just_in_time( ) | .../l10n.php:1408 |
| 19 | 0.2824 | 12630424 | _doing_it_wrong( ) | .../l10n.php:1378 |
| 20 | 0.2824 | 12631256 | wp_trigger_error( ) | .../functions.php:6054 |
| 21 | 0.2828 | 12631896 | trigger_error ( ) | .../functions.php:6114 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5632 | 19800800 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:318 |
| 12 | 0.5632 | 19801128 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5634 | 19800744 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:319 |
| 12 | 0.5634 | 19801064 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5637 | 19800936 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:323 |
| 12 | 0.5637 | 19801256 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5638 | 19800824 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:331 |
| 12 | 0.5638 | 19801144 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5643 | 19824552 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:408 |
| 12 | 0.5643 | 19824872 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.5644 | 19824600 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:434 |
| 12 | 0.5644 | 19824920 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.6429 | 20597024 | WP_REST_Server->send_headers( ) | .../class-wp-rest-server.php:472 |
| 12 | 0.6429 | 20597024 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:1905 |
| 13 | 0.6430 | 20597504 | header ( ) | .../class-wp-rest-server.php:1893 |
| ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /home/ecommerceaggregators.com/public_html/wp-includes/functions.php:6114) in /home/ecommerceaggregators.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893 | ||||
|---|---|---|---|---|
| Call Stack | ||||
| # | Time | Memory | Function | Location |
| 1 | 0.0001 | 360312 | {main}( ) | .../index.php:0 |
| 2 | 0.0001 | 360688 | require( '/home/ecommerceaggregators.com/public_html/wp-blog-header.php' ) | .../index.php:17 |
| 3 | 0.4813 | 17648680 | wp( ) | .../wp-blog-header.php:16 |
| 4 | 0.4813 | 17648712 | WP->main( ) | .../functions.php:1336 |
| 5 | 0.4813 | 17648712 | WP->parse_request( ) | .../class-wp.php:813 |
| 6 | 0.4819 | 17667728 | do_action_ref_array( ) | .../class-wp.php:418 |
| 7 | 0.4819 | 17667728 | WP_Hook->do_action( ) | .../plugin.php:565 |
| 8 | 0.4819 | 17667728 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:348 |
| 9 | 0.4819 | 17668480 | rest_api_loaded( ) | .../class-wp-hook.php:324 |
| 10 | 0.5631 | 19800976 | WP_REST_Server->serve_request( ) | .../rest-api.php:449 |
| 11 | 0.6429 | 20597024 | WP_REST_Server->send_headers( ) | .../class-wp-rest-server.php:472 |
| 12 | 0.6432 | 20613408 | WP_REST_Server->send_header( ) | .../class-wp-rest-server.php:1905 |
| 13 | 0.6432 | 20613728 | header ( ) | .../class-wp-rest-server.php:1893 |
Over the past couple of weeks, Richard and I have spent time at the sharp end of some of the biggest transactions we have seen to date.<\/p>\n
It’s been fascinating to observe the due diligence<\/a> on these deals which, unsurprisingly, has been more involved than usual.<\/p>\n This leads me to the purpose of today’s blog post.<\/p>\n You see:<\/p>\n Whilst the vast majority of sellers obsess over their bottom-line exit valuation, very few focus on the legal and compliance side of selling their Amazon business<\/a>.<\/p>\n The latter, we would argue, is infinitely more important.<\/p>\n And so, after six months of in-house blogs and industry updates<\/a> from yours truly, we decided to mix things up this week.<\/p>\n Step forward, Paul Rafelson.<\/p>\n Paul’s practice, Rafelson Law PLLC, has facilitated the sale of more than 60 Amazon businesses. He is also well-known in the FBA community for his sterling work on Sales Tax, IP disputes, and suspensions.<\/p>\n In other words:<\/p>\n It’s fair to say that Mr Rafelson knows a thing or two about the legal side of selling your Amazon businesses.<\/p>\n So if you are considering an exit in 2022, I would strongly encourage you to read on.<\/p>\n Take it away, Paul.<\/p>\n By Paul Rafelson<\/p>\n So you\u2019ve made the monumental decision as an Amazon FBA seller to sell your private label brand. Congratulations are in order because the blood, sweat, and tears that went into scaling your ecom empire were no small feat.<\/p>\n Unfortunately, too many Amazon sellers don\u2019t understand the magnitude of what a sale actually entails. Often the exit of an Amazon FBA business<\/a> can be riddled with confusion, entail arduous contracts, and result in bad deals that have long-term consequences.<\/p>\n Selling your private label business comes with a heavy assignment. Understand the process, understand the requirements, and understand the legal hygiene required to make your sale as smooth as possible to live out your dreams successfully with far less headache.<\/p>\n In this article, I\u2019ll outline some examples of the challenges that come along with selling your business. And some examples of the key legal hygiene required to sell your Amazon business with confidence.<\/p>\n In a nutshell? Everything. Selling your FBA business is not like selling your car.<\/p>\n While some of you reading this article are shaking your heads in agreement, the truth is most sellers either don\u2019t know what to expect. Or mistakenly believe this process is similar to other personal transactions.<\/p>\n Hence why we say an Amazon FBA exit is not like the ease of selling your vehicle, or just a little more stressful, the sale of your house.<\/p>\n The truth is, the sale of an Amazon business is extensive. The process of selling your Amazon business entails a series of (legal) documents. Including the bible of all documents in most deals called the asset purchase agreement.<\/p>\n The asset purchase agreement<\/a> is essentially the roadmap of the deal and lays out the terms of the deal, establishes the level of risk each party will maintain and determines how the assets of the business will be transferred to the buyer.<\/p>\n Typically the asset purchase agreement begins with a recital of the parties involved, the buyer, seller and sometimes the owner of the company. The agreement serves as a roadmap for the mechanics of the sale transaction.<\/p>\n From there, the asset purchase agreement dives into a series of sections outlining the terms of the deal, including what\u2019s being sold, what\u2019s being excluded, how much is being paid, and what the process for closing will be.<\/p>\n After laying out the basics, as described above, the asset purchase agreement will typically move into what is known as the representations and warranties.<\/p>\n Representations are warranties is a fancy term for promises that both parties make to the other party. The Buyer\u2019s list of representations and warranties is usually much shorter and isn\u2019t as risky as the Seller\u2019s list. The Seller\u2019s list of \u201cpromises\u201d relates to the actual business being sold, and more often than not, the Seller doesn\u2019t know if what they\u2019re \u201cpromising\u201d is true.<\/p>\n For example, you might rep and warrant that you are the true owner of the business and have all authorization required to enter into the transaction.<\/p>\n See how that is essentially<\/em> a promise?<\/p>\n If your promise turns out not to be true, you have a problem, you are in breach of contract, and the buyer can sue to recover damages, losses, etc.<\/p>\n By now, you can see why this is important. Imagine, for example, if you were buying your neighbor\u2019s house.<\/p>\n This person has been your neighbor for 10 years, they are moving to Puerto Rico to save on taxes, and you want to buy it. You presume that because your neighbor has been living there that they have the right to sell the house to you.<\/p>\n But what if, on closing day, your neighbor was unwilling to promise that she actually had title to the house that you were going to buy?<\/p>\n Would you feel comfortable buying it knowing that your neighbor could have been a squatter all this time? Of course not; that\u2019s why each party’s ability to make these promises are important.<\/p>\n Now, while a fundamental promise like that is apparent, what other promises are you being asked to make when you exit your FBA business?<\/p>\n Well, pretty common ones include a promise that you comply with all laws.<\/p>\n Now you might be thinking, \u201cI run a tight ship,\u201d \u201cI\u2019m a law-abiding person, always following the rules,\u201d and \u201cI have no problem making that promise.\u201d<\/p>\n But what if you don\u2019t actually<\/em> know all of the laws?<\/p>\n Maintaining compliance with laws applicable to the business is essential to the exit of your Amazon business, and ensuring that you meet these requirements from the time you start selling to when you exit is paramount. It\u2019s almost impossible for any seller (or lawyer for that matter) to know if their business has been 100% compliant with every law applicable to them. For example, how would a seller know if they complied with every environmental law of every city, state, or country that they have conducted business in?.<\/p>\n You’d be surprised just<\/em> how many sellers don\u2019t meet regulatory compliance and the sticky situations that can ensue mid-deal from not maintaining compliance from conception.<\/p>\n Many product categories like supplements and electronics operate with stringent regulatory compliances to ensure the health and safety of customers. But, compliance with all laws in the context of an international e-commerce business is a very different concept than compliance with all laws when you run a local pizzeria.<\/p>\n Like we said, if not careful can turn a sale upside down.<\/p>\n When it comes to selling an e-commerce business, we need to consider all laws, federal, state, local, international; basically, anywhere you operate as an e-commerce business.<\/p>\n That\u2019s pretty overwhelming, but fortunately, there are ways to mitigate the risk by looking at the products you sell and the requirements applicable to your business ahead of time and ensuring compliance with those requirements before going to market to sell your business.<\/p>\n For example, if you sell products marketed to kids, you may have specific Consumer Product Safety testing requirements; make sure you are compliant before going to market.<\/p>\n Certain products that go in or on the body may have to be made to specific Food and Drug Administration standards or requirements that the products are made in certified labs; same know your compliance before going to market. Knowing your product, market, and core compliance obligations is crucial.<\/p>\n The first that comes to mind here is compliance with all of Amazon\u2019s terms of service. Did you use a review service that was a violation of TOS? Are there other things you did that may have unknowingly been a violation? These are examples of the types of Amazon compliance that will play an essential role in making your sale smooth.<\/p>\n Here are a few examples of compliances sellers often overlook:<\/p>\n For sellers who chose not to use GS1 barcodes at the outset and went with cheap alternative barcodes instead, their accounts can face suspension after closing, even if it relates to something they did pre-closing.<\/p>\n The title to your IP (Intellectual Property) is as valuable as the title to your house. A trademark co-owned by you and your former best friend, who you don\u2019t talk to anymore, is not a good title.<\/p>\n Creatives such as photos and images that sellers mistakenly get from stock photo websites or \u2018borrow\u2019 from Google images<\/a> often can\u2019t be transferred.<\/p>\n If you hired a photographer, you might not have known that most photographers do not give ownership to the photos. Instead, you have to have a license to use their images for the intended purposes, often without the right to assign them, which is crucial when selling your Amazon business.<\/p>\n Maybe you hired someone on Fiverr to put a bunch of content and images together. Do you own the rights to that content and images, or does the Fiver freelancer own the rights? Where did the Fiver freelance get their images from?<\/p>\n Creative compliances are very significant and tend to come up in almost every deal. It\u2019s frustrating for us as lawyers and unnecessarily stressful and confusing for you, the seller.<\/p>\n If you\u2019re promising that you own 100% of the rights to your creative content, but it turns out you did not (e.g., if you used images from Google or hired a freelancer from sites such as Fiverr), you\u2019re in breach of contract. These kinds of breaches can cost you your earn-out payment and allow the buyer to claim the money they paid you for your business. Especially if they are exposed to claims from the content creator, or worse, depending on how your deal is negotiated.<\/p>\n Compliance doesn\u2019t have to be daunting, and it doesn’t have to thwart your sale. All it takes is a little prevention and legal hygiene. Thankfully, there are ways to try and mitigate that risk in a deal if you haven\u2019t done your homework, but it\u2019s still always better to know these things before you go to market so they don\u2019t become an issue during the sale transaction.<\/p>\n To have absolute<\/em> confidence in the sale of your FBA business before you go to market, it is advised that you have a lawyer look over your business. The more hygienic your business is at the outset, the more valuable your FBA business will be. And the less risk you\u2019ll assume if some of those promises you made turn out not to be true.<\/p>\n Ensuring compliance and appropriate legal hygiene means a smoother selling process and closing. But even if it\u2019s past that point, and you are already at the offer stage or even in the purchase agreement, you should always have a lawyer represent you, so that at the very least you understand the risks related to your deal, including your potential personal liability.<\/p>\n So, if a broker or a buyer ever tells you that all you need to do is sign, it\u2019s just boilerplate, no need to get the lawyers involved (and this happens), trust me you should run away. In an M&A transaction that is almost never going to be the case.<\/p>\n Questions about the sale of your Amazon FBA business? Initial consultations regarding the sale of your business are always complimentary. As a law firm that understands the market, Amazon businesses and the law, we are excited to help you through this complicated but exciting process. Contact us<\/a> at any time to set up an introduction call.<\/p>\n\n
\nThe Anatomy of A Business Sale<\/h2>\n
What Does the Asset Purchase Agreement Have to Do with the Sale of Your Amazon FBA Business?<\/h3>\n
What Are Representations & Warranties And Why Are They Important?<\/h3>\n
What is Compliance, and Why Is it Vital to The Exit of Your FBA Business?<\/h3>\n
What Other Types Of Compliance Are Crucial To Your Sale?<\/h3>\n
UPC Barcodes<\/h4>\n
Title to IP<\/h4>\n
Creative Assets<\/h4>\n
Summary<\/h3>\n