EMIX use cases showing requirements for defining geographic regions

I'm looking for any EMIX use cases that show there is a requirement for  defining a geographic region when communicating price and/or product  information.  I know the discussion started some time ago, but don't  recall the reason/driver.  I know about California tiered pricing based  on climate zones as one example, but am assuming there are more ...  Thanks, -A