Method and system of online shopping via third party using blog

Abstract

A system of online shopping via a sales agent includes user terminals ( 1 ); seller terminals ( 21 ); sales agent terminals ( 22 ); two web servers ( 3 ) wherein one web server ( 3 ) comprises a seller blog ( 31 ) including item description web pages ( 3 W 1 ), and the other web server ( 3 ) comprises a sales agent blog ( 32 ) including item web pages ( 3 W 2 ); an online billing platform ( 4 ); and bank terminals ( 5 ). The user terminals ( 1 ), the seller terminals ( 21 ), the sales agent terminals ( 22 ), the web servers ( 3 ), the online billing platform ( 4 ), and the bank terminals ( 5 ) are connected together via the Internet ( 6 ). Methods of online shopping via a third party (e.g., sales agent or OEM) using a blog are also provided.

1. A method of online shopping comprising the steps of:
 at a seller: 
 using a seller terminal ( 23 ) to access a seller blog ( 33 ) over the Internet ( 6 ); and 
 creating a first item description web page ( 3 W 1 ) in the seller blog ( 33 ) wherein at least one picture and accompanying description of at least one item being sold are posted on the first item description web pages ( 3 W 1 ); 
 at a reseller: 
 using a reseller terminal ( 24 ) to access a reseller blog ( 34 ) over the Internet ( 6 ); and 
 creating a second item description web page ( 3 W 1 ) in the reseller blog ( 34 ) wherein at least one picture and accompanying description of at least one item being sold are posted on the second item description web page ( 3 W 1 ); 
 at a manager of an online billing platform ( 4 ): 
 manufacturing at least one original equipment manufacturer (OEM) product based on a combination of the at least one item posted on the first item description web page ( 3 W 1 ) and the at least one item posted on the second item description web page ( 3 W 1 ); 
 creating an OEM merchandise file ( 431 D) in a merchandise database ( 431 ); 
 creating tab program codes (PC) in a program database ( 461 ); and 
 creating a plurality of OEM merchandise sale web pages ( 43 W 2 ) by the OEM merchandise file ( 431 D) wherein each of the OEM merchandise sale web pages ( 43 W 2 ) includes a payment tab, a first link tab, and a second link tab; 
 at a buyer: 
 clicking the first link tab of the OEM merchandise sale web pages ( 43 W 2 ) to link a platform server ( 41 ) of the online billing platform ( 4 ) to the first item description web page ( 3 W 1 ) for viewing the at least one picture and accompanying description of the at least one item being sold on the first item description web page ( 3 W 1 ); and 
 clicking the second link tab of the OEM merchandise sale web pages ( 43 W 2 ) to link the platform server ( 41 ) to the second item description web page ( 3 W 1 ) for viewing the at least one picture and accompanying description of the at least one item being sold on the second item description web page ( 3 W 1 ); 
 at the seller: 
 using the seller terminal ( 23 ) to link to a seller blog ( 33 ); 
 creating a first OEM merchandise web page ( 3 W 3 ) in the seller blog ( 33 ) wherein at least one picture and accompanying description of at least one item being sold are posted on the first OEM merchandise web page ( 3 W 3 ); 
 using the seller terminal ( 23 ) to link to the platform server ( 41 ) and a member web page ( 42 W) of a login server ( 42 ) of the online billing platform ( 4 ); 
 applying for membership; 
 using the seller terminal ( 23 ) to access the platform server ( 41 ); 
 linking to the login server ( 42 ); 
 logging in for gaining access to a program database ( 461 ); 
 copying program codes of an OEM tab program (P 2 ) to the seller terminal ( 23 ); 
 copying the program codes of the OEM tab program (P 2 ) to the seller blog ( 33 ); 
 installing a purchase confirmation tab, a guide tab, and the program codes of the OEM tab program (P 2 ) in the first OEM merchandise web page ( 3 W 3 ); 
 logging in for obtaining the tab program codes (PC) by linking to the program database ( 461 ); 
 using the seller terminal ( 23 ) to link to the seller blog ( 33 ) and copy the tab program codes (PC) to the seller blog ( 33 ); and 
 linking the first OEM merchandise web page ( 3 W 3 ) to the platform server ( 41 ) and the OEM merchandise sale web page ( 43 W 2 ); 
 at the buyer: 
 using a user terminal ( 1 ) to link to the seller blog ( 33 ) for viewing the at least one picture and accompanying description of the at least one item being sold on the first OEM merchandise web page ( 3 W 3 ); 
 clicking the purchase confirmation tab on the first OEM merchandise web page ( 3 W 3 ); linking the first OEM merchandise web page ( 3 W 3 ) to the platform server ( 41 ) and the OEM merchandise sale web pages ( 43 W 2 ); and 
 buying one or more OEM items posted on the OEM merchandise sale web pages ( 43 W 2 ) by clicking the payment tab thereon; 
 at the reseller: 
 using the reseller terminal ( 24 ) to link to the reseller blog ( 34 ); 
 creating a second OEM merchandise web page ( 3 W 3 ) in the reseller blog ( 34 ) wherein at least one picture and accompanying description of at least one item being sold are posted on the second OEM merchandise web page ( 3 W 3 ); 
 using the reseller terminal ( 24 ) to link to the platform server ( 41 ) and the member web page ( 42 W); 
 applying for membership; 
 using the reseller terminal ( 24 ) to link to the platform server ( 41 ) and the login server ( 42 ); 
 logging in for gaining access to the program database ( 461 ); 
 copying the program codes of the OEM tab program (P 2 ) to the reseller terminal ( 24 ); 
 copying the program codes of the OEM tab program (P 2 ) to the reseller blog ( 34 ); 
 installing the purchase confirmation tab, the guide tab, and the program codes of the OEM tab program (P 2 ) in the second OEM merchandise web page ( 3 W 3 ); 
 logging in for obtaining the tab program codes (PC) by linking to the program database ( 461 ); 
 copying the tab program codes (PC) to the reseller blog ( 34 ); 
 clicking the purchase confirmation tab on the second OEM merchandise web page ( 3 W 3 ); 
 linking the second OEM merchandise web page ( 3 W 3 ) to the platform server ( 41 ) and the OEM merchandise sale web pages ( 43 W 2 ); 
 buying one or more OEM items posted on the OEM merchandise sale web pages ( 43 W 2 ) by clicking the payment tab thereon; 
 using the reseller terminal ( 24 ) to link to the reseller blog ( 34 ) for viewing the at least one picture and accompanying description of the at least one item being sold on the second OEM merchandise web page ( 3 W 3 ); 
 buying an OEM item sold on the second OEM merchandise web page ( 3 W 3 ) by clicking the purchase confirmation tab on the second OEM merchandise web page ( 3 W 3 ) which is in turn linked to the platform server ( 41 ) and the OEM merchandise sale web pages ( 43 W 2 ); and 
 clicking the purchase confirmation tab on the second OEM merchandise web page ( 3 W 3 ) to link to the platform server ( 41 ) and the login server ( 42 ); 
 at the buyer: 
 logging in for linking to a payment web page ( 44 W 1 ) of a billing server ( 44 ) of the online billing platform ( 4 ); 
 inputting payment data on the payment web page ( 44 W 1 ); 
 creating a purchase order file with order number ( 441 D) in a purchase order database ( 441 ) of the billing server ( 44 ) based on the payment data; 
 linking the platform server ( 41 ) to a bank terminal ( 5 ); 
 enabling the billing server ( 44 ) to verify credit card information provided in the purchase order file with order number ( 441  D) with a credit card issuing bank; 
 creating a transaction particulars file with order number ( 442 D) in a bank database ( 442 ) of the billing server ( 44 ) based on an authorization from the credit card issuing bank; and 
 creating a shipment file with order number ( 443 D) in a shipment database ( 443 ) of the billing server ( 44 ); 
 at an e-mail server: 
 enabling an e-mail server ( 45 ) to send an e-mail including the purchase order file with order number ( 441  D) to the buyer; 
 enabling the e-mail server ( 45 ) to send an e-mail to the seller to prepare the bought OEM item and ship same to the reseller based on the shipment file with order number ( 443 D); and 
 enabling the e-mail server ( 45 ) to send an e-mail to the reseller to manufacture the bought OEM item after receiving the OEM item from the seller based on the shipment file with order number ( 443 D); 
 at the reseller: 
 shipping the manufactured OEM item to the buyer based on the shipment file with order number ( 443 D); 
 at the seller: 
 after the shipment, using the seller terminal ( 23 ) to link to the platform server ( 41 ) and the login server ( 42 ); 
 logging in for linking to a request for payment web page ( 44 W 2 ) of the billing server ( 44 ); 
 inputting request for payment data on the request for payment web page ( 44 W 2 ); and 
 creating a debit note file with order number ( 444 D) in a request for payment database ( 444 ) of the billing server ( 44 ) based on the request for payment data; 
 at the reseller: 
 after the shipment, using the reseller terminal ( 24 ) to link to the platform server ( 41 ) and the login server ( 42 ); 
 logging in for linking to a request for payment web page ( 44 W 2 ) of the billing server ( 44 ); 
 inputting request for payment data on the request for payment web page ( 44 W 2 ); 
 creating a debit note file with order number ( 444 D) in a request for payment database ( 444 ) of the billing server ( 44 ) based on the request for payment data; and 
 after being verified by the manager of the online billing platform ( 4 ), preparing an invoice and sending same to the buyer for request for payment.