Zoho data structure setup for e-commerce referral program - zoho

Building custom integration for a client with their e-commerce store and Zoho. They essentially have a referral program, for the easiest explanation. When someone purchases, we need to keep track of who the referring person was in Zoho and credit them - I have this all available. They only sell 1 product so we don't need actual financial / sales data, just the number of units attributed to the person in Zoho. They eventually want to be able to have reports generated in Zoho to tell them how many units each person is doing per month, who is their best performer, etc.
All the potential referral people are stored as Contacts in Zoho. My task is simply getting the data from the e-commerce site into Zoho, I do not have to create any reports or anything within Zoho. I have no experience with the Zoho world so I am not quite sure where the best place to even put this data as there are so many different Zoho "things" to use. I thought about using Invoices, but again we don't necessarily need the transaction data just counts and when they happened to produce the above stated reports.

I was finally able to reach someone at Zoho: Sales Orders are the right place to put this.

Related

Transactions in plaid - categories

I'm looking to build a budgeting app where users can categories transactions (i.e. entertainment, rent, utilities, etc).
Is it possible to categorize plaid transactions by needs/wants? aka rent is under the need category, restaurants are under a want category.
I've looked here but am struggling to find any info: https://plaid.com/docs/api/products/#auth
You can use the /categories/get endpoint to see all the categories used by Plaid. From there, it should be pretty straightforward to essentially create a mapping where for each category you classify it as a need or a want. (This is a determination you'd have to make yourself; need/want info is not built into the API.)

Google Play Invoicing: Which entity should be the recipient of an Invoice for selling IAPs?

I'm from EU (not Ireland) and need to invoice one of the Google entities for all IAP transactions that were in my app in the last month but I just can't, for the love of me, find any info on any of my accounts as to whom should I invoice. I realize that I don't need to actually send the invoice anywhere if I'm from outside of Ireland but I still need to create the invoice for the sake of taxes in my country.
I found two Google entities that might be suitable but am still not sure which one will it be (as I didn't actually receive the payment yet):
GOOGLE IRELAND LIMITED vat number: IE 6388047 V
GOOGLE COMMERCE LIMITED vat number: IE 9825613 N
Does any one have any experience with that and could point me in the right direction?
Another question is about the Google commission. As far as I know, I can count this commission as income cost but I'm still not sure on how to do that properly yet. Will I get an Invoice for this amount from Google after the actual payment is done? Or do I have to calculate this value from the monthly reports available in Google Play Console?
Any help would be greatly appreciated.

How to handle price dynamic

We have requirement to handle price dynamic (referring external system).
We would like to know, what is the best way to handle dynamic pricing among below :
Approach 1 :
Creating Price factory extension and overriding getBasePrice() method of customPricefactoryManager. Please confirm if it uses jalo layer.
Approach 2 :
In DefaultSLFindPriceStrategy we can customize getBasePrice() method.
If any other way too, please lets know.
We would like to know which approach can help to handle prices in addtocart operation, checkout and product page details pricing.
It is not good getting price in another system with integration online. ERP system used by few sales people but ecommerce site can be used by hundred customer in same time. ERP cannot be handle huge amount of connections. I prefer pushing price from ERP not pulling them from hybris side. On the other hand customer will be hate changing price while surfing between hybris pages. You need to plan correct time for updating price and re-calculating existing carts.
It is highly unlikely that you would need to override the above classes to get dynamic prices.
Hybris already provides OTB functionality to get prices for different-
Users
User groups
Currencies
Time range
If you are trying to get different prices based on above criterions then you can simply use the OTB price row model.Getting dynamic prices on different pages has many caveats-
The price on different pages i.e. Homepage, PDP, Cart, Checkout,
etc. might show different values confusing the customer.
It cannot
be indexed so the PLP page will almost always show a different price
value.

Schema.org microdata for marketplace

For a marketplace, schema data becomes more confusing. Not only will you want to represent your organization, but you also have the supplier's organization to worry about. Is it bad practice to have all of this data on one page? Should the product page only have product information in the metadata, and the local business only have local business details on it?
Marketplace Org
logo
name
description
LocalBusiness Org
logo
name
description
address
lat/long
product
description
rating
price
I can provide html for all of this, but I am not sure this needs it to explain. I read the schema docs pretty in-depth but it doesn't have great examples of what a marketplace site would do with multiple organizations or what Google will think of it. For instance, if there is a localbusiness with many products, is it proper to have an aggregate rating on the localbusiness page of all of their products combined into one rating?
Is it bad practice to have all of this data on one page?
No. The more the better! (Of course it may be the case that some consumers only like to work with a single item per page, but when it comes to this topic, anything might be possible. So when you are interested in a particular consumer, you should consult their documentation.)
Every itemscope creates a new item. Every item on a page is (… should be) about something different.
So don’t create several items for the same thing on the same page (unless you can use itemid so that it’s clear that the items are about the same thing).
If possible, use properties to relate the items.
For example, LocalBusiness has the property makesOffer to point "to products or services offered by the organization" (i.e., Offer), or the property owns for products "owned by the organization" (i.e., Product).
You can associate a Product via brand or manufacturer with an Organization (resp. LocalBusiness).

Solving the location-based app data problem

I'm trying to build a very simple location-based app and I have all of these services at my disposal (Foursquare API, SimpleGeo, Google Places, etc). All seem to provide me a list of venues (bars, coffee shops, stores, etc) near a given longitude latitude. This is great but once the users see the venues, they will be able to write reviews about each venue (for example). Now, what do I do with this data?
User ID (users for my app)
Venue Name (retrieved from Foursquare API)
Longitude, Latitude
Foursquare Venue ID
Review
Do I store this in my database? What happens if the venue name changes on the Foursquare servers? If I don't store this in my database, I'd have to do a lookup to retrieve the venue name and details every single time I want to return a list of reviews in the area. Can someone offer some advice on how to conceptually design a venue-based location app. Thanks.
Store the essential 3rd party info in your database but treat it as a cache. Have a background task that checks for updates every few minutes, days, or weeks depending on the likelyhood & severity of changes. In between updates the user may get stale data but hey, that's life... at least they got it fast. In doing your updates, don't update everything at once or you'll run quickly into API throttling limits.

Resources