Re: [WebDNA] Sales Tax on CUstom WebDNA Site

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101313
interpreted = N
texte = JD Ready wrote: > Hi Gang, > > Hoping someone can help out here... > > I have a custom webdna site that I inherited (www.tennis-apparel.com > ). I believe that it is custom in that I > don't think it uses the "Store Builder" code from the admin menu. The > original owners of the site were located in Montana which does not > collect sales tax. We have now moved the site to a suburb of Denver, > CO. So I need to calculate State tax on in-state sales, but I'm also > concerned with the county, city, and RTD tax for local buyers. So my > questions are: > > 1) Should I be concerned with all of those, or just the State? I think the term nexus usually still applies.. but yea, like Bob said.. (nexus is basically calculating the tax for where your server is and/or, where your majority of sales are done) > 2) What is the typical way for a webDNA site to handle these things? Well, if you are using the orderfile tags, you will probably want to become familiar with the orderfile and how it works. > 3) Can someone point me in the right direction for calculating these issues? > > Thanks in advance for any help in this regard! Sincerely, For right now, I think the best way to get familiar with the sites "shopping functions" is by studying the orderfile tags.. docs.webdna.us Click on "at a glance". Study all the tags (contexts/commands) under that heading. We used to have a good "WebMerchant" manual that explained how those all work together, but has since gone missing. The new owners will have to remake some documentation once we rework SiteBuilder. ;-) Anyway, first study those tags, then maybe look at the example stores that come with the software (tea room etc.). We can help you with any specific questions. For Taxes, click on the "Purchase" command under the "shopping" header. This page shows you all of the pre-built "orderfile tags". You will find the tax related fields *can* be set manually using setheader etc.. However, the automated system works very generally like this: You have a core products database called "products.db". Inside that products database you have certain fields that must be written specifically... such as "price" "sku" "taxable" etc. These fields work with the Formulas.db to make sure products are added the orderfile correctly. (see the docs under "file formats" for the formulas.db and orderile) The formulas.db is like it implies... The Formulas.db dictates certain things (product cost, taxes, and shipping) upon adding an item to the database. chances are if you are using orderfile tags, that this file may exist already. So between all these components, there is some automation that I must admit is not documented too well anymore. This will change at some point because this system is a real time saver in many applications, and is still valid today. Anyway, the important thing to know is that there is plenty of ways to get the exact function that you are looking for when working in WebDNA. First, find out what you need to do, then we will help you with a solution. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Sales Tax on CUstom WebDNA Site (Donovan Brooke 2008)
  2. Re: [WebDNA] Sales Tax on CUstom WebDNA Site (Bob Minor 2008)
  3. [WebDNA] Sales Tax on CUstom WebDNA Site ("JD Ready" 2008)
JD Ready wrote: > Hi Gang, > > Hoping someone can help out here... > > I have a custom webdna site that I inherited (www.tennis-apparel.com > ). I believe that it is custom in that I > don't think it uses the "Store Builder" code from the admin menu. The > original owners of the site were located in Montana which does not > collect sales tax. We have now moved the site to a suburb of Denver, > CO. So I need to calculate State tax on in-state sales, but I'm also > concerned with the county, city, and RTD tax for local buyers. So my > questions are: > > 1) Should I be concerned with all of those, or just the State? I think the term nexus usually still applies.. but yea, like Bob said.. (nexus is basically calculating the tax for where your server is and/or, where your majority of sales are done) > 2) What is the typical way for a webDNA site to handle these things? Well, if you are using the orderfile tags, you will probably want to become familiar with the orderfile and how it works. > 3) Can someone point me in the right direction for calculating these issues? > > Thanks in advance for any help in this regard! Sincerely, For right now, I think the best way to get familiar with the sites "shopping functions" is by studying the orderfile tags.. docs.webdna.us Click on "at a glance". Study all the tags (contexts/commands) under that heading. We used to have a good "WebMerchant" manual that explained how those all work together, but has since gone missing. The new owners will have to remake some documentation once we rework SiteBuilder. ;-) Anyway, first study those tags, then maybe look at the example stores that come with the software (tea room etc.). We can help you with any specific questions. For Taxes, click on the "Purchase" command under the "shopping" header. This page shows you all of the pre-built "orderfile tags". You will find the tax related fields *can* be set manually using setheader etc.. However, the automated system works very generally like this: You have a core products database called "products.db". Inside that products database you have certain fields that must be written specifically... such as "price" "sku" "taxable" etc. These fields work with the formulas.db to make sure products are added the orderfile correctly. (see the docs under "file formats" for the formulas.db and orderile) The formulas.db is like it implies... The formulas.db dictates certain things (product cost, taxes, and shipping) upon adding an item to the database. chances are if you are using orderfile tags, that this file may exist already. So between all these components, there is some automation that I must admit is not documented too well anymore. This will change at some point because this system is a real time saver in many applications, and is still valid today. Anyway, the important thing to know is that there is plenty of ways to get the exact function that you are looking for when working in WebDNA. First, find out what you need to do, then we will help you with a solution. Donovan -- Donovan D. Brooke PH/FAX: 1 (608) 291-2024 ---------------------------------------------- VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] 8.0.2 Install on Yosemite Fails (2015) MacWEEK article help needed (1996) List Last Word (2002) taxTotal confusion (1998) Cancel Subscription (1996) Am I going senile? (Price recalc based on quantity) (1997) Custom WebCat Prefs ... (1997) can we get string variables? (1998) A quickie question (1997) WebCatalog for Postcards ? (1997) [WebDNA] sendmail attached file (2011) Customizing WebDelivery.html (1998) Document Contains No Data! (1997) Summary layout (1997) looping table rows (1999) WebCat2 several catalogs? (1997) PCS Frames (1997) PSC recommends what date format yr 2000??? (1997) [WebDNA] MailChimp (2012) form data submission gets truncated (1997)