Sage 100

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

Thank you, this is very helpful to know. I unfortunately wasn't involved when the customer spoke with and ultimately engaged Avalara. The feedback they provided me about being shuffled from one person to another is very familiar.

This company is very unsophisticated and I think they are a little overwhelmed and uncertain about how much help Avalara will provide for both setup and ongoing assistance.

I have seen another Sage partner recommend that VARS become engaged with Avalara right from the start or you risk being the "unpaid complaint department" for what Avalara may promise. I do think for this 3rd party solution that VARS need to make clear that if they are not retained to work with Avalara that the customer should expect to navigate some tricky waters and know all the questions to ask. 

Right now I'm getting a lot of "oh, we didn't realize that" type questions and having to decide whether to get rid of Avalara or stay the course. Unfortunately, there doesn't seem to be a viable alternative so I suspect this customer will stay.

1. The inventory remains at their warehouse.
2. They list the inventory online in the marketplace
3. A customer buys from the marketplace
4. The marketplace processes the sale in full - including sales tax ( which most marketplaces are now tasked with collecting and remitting )
5. My customer then receives this order from the marketplace, they create an account for the person who bought the item ( which is shown on the order that the marketplace sends to my customer)  and then they ship the product from their warehouse.

I guess they could create a separate sales tax code for marketplace sales however I believe some states have requirements that when you report sales for the purpose of nexus they want to know taxable, nontaxable, and perhaps marketplace-based sales.

I'm concerned that if I don't set marketplace sales to go through Avalara then the customer is paying $$ for a sales tax service that they may not be fully utilizing.

To be fair, Avalara does include knowledge articles regarding this topic but the "how-to" of the setup isn't immediately clear to me.

https://help.avalara.com/Avalara_AvaTax_Update/Add_marketplace_transactions_to_your_company_profile

I wish I had been included in the initial discussions with Avalara because now it's impossible for me to know exactly what was promised ( or what the customer THOUGHT they heard ). The issue with this particular transaction is Avalara says the customer chose to self-install and this customer is very inexperienced and I doubt they will be able to self-install.

Except if a company is ALREADY an Avalara customer who is adding more company codes - the implementation charge seems like it should be added automatically to the sale and not an option. 

Now I have to convince the customer that they need to pay Avalara and set their expectation that even after they pay that they will likely still need to project manage Avalara on their own and be diligent about tracking progress. 

@Dana Young did you try setting up an advanced rule? That seems as if it should be the solution but I am not sure the rule works or maybe the connector doesn't bring in the salesperson?

The fallback appears to be if you add an inventory item to the invoice - which the connector definitely should read. It appears you can create an advanced rule to read the item code and where there is a match set the location ( marketplace ) code.

It was easier for the customer to use the salesperson because that's how they were already doing their invoices

I may have to try adding an item number and seeing if the advanced rule picks that up

I​ had a similar conversation with Melissa Craig at Avalara ( she is apparently another mgr of strategic alliances ).  And similar experiences with everyone at Avlara. It's one lengthy series of handing you off to person after person and I now think that is happening because many people are new and they aren't familiar with Sage or Avalara.

​

@Dana Young did you try setting up an advanced rule? That seems as if it should be the solution but I am not sure the rule works or maybe the connector doesn't bring in the salesperson?

The fallback appears to be if you add an inventory item to the invoice - which the connector definitely should read. It appears you can create an advanced rule to read the item code and where there is a match set the location ( marketplace ) code.

It was easier for the customer to use the salesperson because that's how they were already doing their invoices

I may have to try adding an item number and seeing if the advanced rule picks that up

I​ had a similar conversation with Melissa Craig at Avalara ( she is apparently another mgr of strategic alliances ).  And similar experiences with everyone at Avlara. It's one lengthy series of handing you off to person after person and I now think that is happening because many people are new and they aren't familiar with Sage or Avalara.

​