{"id":71571,"date":"2026-08-17T22:22:14","date_gmt":"2026-08-17T20:22:14","guid":{"rendered":"https:\/\/symmy.com\/erpedie\/propojeni-pohody-s-crm\/"},"modified":"2026-08-18T07:42:16","modified_gmt":"2026-08-18T05:42:16","slug":"propojeni-pohody-s-crm","status":"publish","type":"erpedie","link":"https:\/\/symmy.com\/cs\/erpedie\/propojeni-pohody-s-crm\/","title":{"rendered":"Propojen\u00ed POHODY s CRM: co p\u0159en\u00e1\u0161et, \u010dty\u0159i cesty a jak vybrat"},"content":{"rendered":"<p>Obchodn\u00ed t\u00fdm \u017eije v CRM \u2014 Raynet, Pipedrive nebo HubSpot. \u00da\u010detn\u00ed \u017eije v POHOD\u011a. A mezi nimi se p\u0159episuje: nov\u00fd z\u00e1kazn\u00edk ru\u010dn\u011b do \u00fa\u010detnictv\u00ed, vystaven\u00e1 faktura ru\u010dn\u011b ke kontaktu, stav pohled\u00e1vek se zji\u0161\u0165uje dotazem p\u0159es kancel\u00e1\u0159. Tenhle \u010dl\u00e1nek shrnuje, co se mezi CRM a POHODOU d\u00e1 p\u0159en\u00e1\u0161et automaticky, jak\u00e9 \u010dty\u0159i cesty propojen\u00ed existuj\u00ed a podle \u010deho vybrat.<\/p>\n<h2>Kr\u00e1tk\u00e1 odpov\u011b\u010f<\/h2>\n<div class=\"ep-answer\">\n<p>Propojit POHODU s CRM jde v\u017edy \u2014 POHODA m\u00e1 otev\u0159en\u00e9 XML rozhran\u00ed, kter\u00e9 um\u00ed \u010d\u00edst i zapisovat v\u0161echny podstatn\u00e9 agendy. Rozhoduje se mezi <strong>nativn\u00edm dopl\u0148kem CRM<\/strong> (rychl\u00e9, ale co um\u00ed, to um\u00ed), <strong>ru\u010dn\u00ed synchronizac\u00ed exporty<\/strong> (zadarmo, ale n\u011bkdo ji mus\u00ed d\u011blat), <strong>DIY automatizac\u00ed<\/strong> (Make\/Zapier \u2014 nar\u00e1\u017e\u00ed na mServer) a <strong>integra\u010dn\u00ed platformou<\/strong> (stav\u011bn\u00e1 na m\u00edru, hl\u00eddan\u00e1, obousm\u011brn\u00e1). \u010c\u00edm v\u00edc agend a \u010d\u00edm v\u00edc lid\u00ed se syst\u00e9my pracuje, t\u00edm d\u0159\u00edv se vyplat\u00ed posledn\u00ed cesta.<\/p>\n<\/div>\n<h2>Co se mezi CRM a POHODOU p\u0159en\u00e1\u0161\u00ed<\/h2>\n<ul class=\"ep-cards\">\n<li><strong>Z\u00e1kazn\u00edci a kontakty<\/strong>Nov\u00e1 firma v CRM se zalo\u017e\u00ed jako adres\u00e1\u0159 v POHOD\u011a \u2014 s I\u010cO, DI\u010c a faktura\u010dn\u00ed adresou. Obousm\u011brn\u011b: zm\u011bna faktura\u010dn\u00edch \u00fadaj\u016f v \u00fa\u010detnictv\u00ed se prop\u00ed\u0161e zp\u011bt obchodn\u00edkovi.<\/li>\n<li><strong>Faktury a pohled\u00e1vky<\/strong>Vystaven\u00e9 faktury z POHODY se zobraz\u00ed u z\u00e1kazn\u00edka v CRM v\u010detn\u011b stavu \u00fahrady. Obchodn\u00edk vid\u00ed, komu nevolat s novou nab\u00eddkou, dokud dlu\u017e\u00ed.<\/li>\n<li><strong>Produkty a cen\u00edky<\/strong>Skladov\u00e9 karty a ceny z POHODY jako podklad pro nab\u00eddky v CRM \u2014 nab\u00eddka se pak neskl\u00e1d\u00e1 z neaktu\u00e1ln\u00edch cen.<\/li>\n<li><strong>Zak\u00e1zky a objedn\u00e1vky<\/strong>Vyhran\u00e1 p\u0159\u00edle\u017eitost v CRM se prom\u011bn\u00ed v p\u0159ijatou objedn\u00e1vku nebo zak\u00e1zku v POHOD\u011a \u2014 bez p\u0159episov\u00e1n\u00ed polo\u017eek.<\/li>\n<\/ul>\n<h2>\u010cty\u0159i cesty propojen\u00ed<\/h2>\n<ol class=\"ep-steps\">\n<li><strong>Nativn\u00ed dopln\u011bk CRM.<\/strong> N\u011bkter\u00e1 CRM maj\u00ed konektor na POHODU p\u0159\u00edmo v nab\u00eddce dopl\u0148k\u016f. V\u00fdhoda: rychl\u00e9 zapnut\u00ed. Limit: p\u0159en\u00e1\u0161\u00ed jen to, s \u010d\u00edm v\u00fdrobce po\u010d\u00edtal, obvykle jedn\u00edm sm\u011brem a v pevn\u00e9m intervalu \u2014 a s edicemi mimo \u0159adu SQL\/E1 b\u00fdv\u00e1 pot\u00ed\u017e.<\/li>\n<li><strong>Ru\u010dn\u00ed exporty a importy.<\/strong> POHODA um\u00ed XML export\/import, CRM zpravidla CSV. Zadarmo a bez z\u00e1vislost\u00ed, ale synchronizaci mus\u00ed n\u011bkdo pravideln\u011b d\u011blat \u2014 a den, kdy se na ni zapomene, je den, kdy obchodn\u00edk vol\u00e1 dlu\u017en\u00edkovi s novou nab\u00eddkou.<\/li>\n<li><strong>DIY automatizace (Make, Zapier, n8n).<\/strong> Na stran\u011b CRM funguje skv\u011ble, na stran\u011b POHODY naraz\u00ed: mServer b\u011b\u017e\u00ed u v\u00e1s (nen\u00ed ve\u0159ejn\u00e9 cloudov\u00e9 API) a ofici\u00e1ln\u00ed konektor neexistuje. Podrobn\u011b jsme to rozebrali v \u010dl\u00e1nku <a href=\"\/cs\/erpedie\/make-zapier-n8n-pohoda\/\">Make, Zapier, n8n a POHODA<\/a>.<\/li>\n<li><strong>Integra\u010dn\u00ed platforma.<\/strong> Propojen\u00ed postaven\u00e9 na m\u00edru vybran\u00fdm agend\u00e1m, obousm\u011brn\u00e9, s monitoringem a validac\u00ed ka\u017ed\u00e9ho p\u0159enosu. Stavba podle agend (obvykle 6\u201312 hodin pr\u00e1ce na agendu), pak b\u011b\u017e\u00ed samo. Dvojici najdete v <a href=\"\/cs\/systemy-integrace\/\">katalogu integrac\u00ed<\/a> \u2014 nap\u0159\u00edklad <a href=\"\/cs\/integrace\/raynet-pohoda-e1\/\">Raynet + POHODA E1<\/a>.<\/li>\n<\/ol>\n<h2>Specifika POHODY, se kter\u00fdmi je t\u0159eba po\u010d\u00edtat<\/h2>\n<p>POHODA komunikuje p\u0159es XML rozhran\u00ed; pro pr\u016fb\u011b\u017enou synchronizaci se pou\u017e\u00edv\u00e1 <a href=\"\/cs\/erpedie\/pohoda-mserver\/\">mServer<\/a> \u2014 HTTP server, kter\u00fd je sou\u010d\u00e1st\u00ed ka\u017ed\u00e9 POHODY, ale b\u011b\u017e\u00ed na va\u0161em stroji a je pot\u0159eba ho spr\u00e1vn\u011b provozovat. U edic \u0159ady SQL a E1 lze \u010d\u00edst i p\u0159\u00edmo z datab\u00e1ze, co\u017e snese \u010dast\u011bj\u0161\u00ed synchronizaci a v\u011bt\u0161\u00ed objemy. Edice se li\u0161\u00ed i t\u00edm, kolik paraleln\u00edch p\u0159ipojen\u00ed zvl\u00e1dnou \u2014 na tom stoj\u00ed volba intervalu synchronizace.<\/p>\n<h2>Nej\u010dast\u011bj\u0161\u00ed p\u0159\u00edpad: Raynet + POHODA<\/h2>\n<p>\u010cesk\u00e1 kombinace, kterou stav\u00edme nej\u010dast\u011bji: <a href=\"\/cs\/aplikace\/raynet\/\">Raynet<\/a> jako CRM, <a href=\"\/cs\/aplikace\/pohoda\/\">POHODA<\/a> jako \u00fa\u010detnictv\u00ed. Adres\u00e1\u0159 a pohled\u00e1vky te\u010dou obousm\u011brn\u011b, vyhran\u00e9 obchody se m\u011bn\u00ed v objedn\u00e1vky. A pokud t\u00fdm \u017eije v kalend\u00e1\u0159i, synchronizujeme i <a href=\"\/cs\/integrace\/raynet-outlook\/\">Raynet s Outlookem<\/a> \u2014 sch\u016fzky, \u00fapravy a ru\u0161en\u00ed v obou sm\u011brech.<\/p>\n<div class=\"ep-note\">\n<h2>Jedna past: duplicitn\u00ed z\u00e1kazn\u00edci<\/h2>\n<p>Nej\u010dast\u011bj\u0161\u00ed zdroj zmatku v praxi. Obchodn\u00edk zalo\u017e\u00ed \u201eNov\u00e1k s.r.o.\u201c, \u00fa\u010detn\u00ed m\u00e1 v adres\u00e1\u0159i \u201eNOV\u00c1K, spol. s r. o.\u201c \u2014 a integrace bez pravidel vyrob\u00ed t\u0159et\u00ed z\u00e1znam. \u0158e\u0161en\u00ed je p\u00e1rovat podle I\u010cO, ne podle n\u00e1zvu, a ur\u010dit, kter\u00fd syst\u00e9m je pro kter\u00fd \u00fadaj autoritou (faktura\u010dn\u00ed \u00fadaje vede \u00fa\u010detnictv\u00ed, obchodn\u00ed kontakty CRM). Tohle pravidlo nastavujeme p\u0159i ka\u017ed\u00e9 integraci jako prvn\u00ed.<\/p>\n<\/div>\n<h2>\u010cast\u00e9 ot\u00e1zky<\/h2>\n<details class=\"ep-faq\">\n<summary>Kolik propojen\u00ed POHODY s CRM stoj\u00ed?<\/summary>\n<p>U integra\u010dn\u00ed platformy se cena odv\u00edj\u00ed od po\u010dtu agend \u2014 z\u00e1kladn\u00ed propojen\u00ed jedn\u00e9 agendy vyjde podle typu na 6\u201312 hodin pr\u00e1ce, p\u0159esn\u00fd rozsah se up\u0159es\u0148uje po \u00favodn\u00ed sch\u016fzce. Nativn\u00ed dopl\u0148ky m\u00edvaj\u00ed m\u011bs\u00ed\u010dn\u00ed pau\u0161\u00e1l, ru\u010dn\u00ed synchronizace stoj\u00ed \u010das \u010dlov\u011bka, kter\u00fd ji d\u011bl\u00e1.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Funguje propojen\u00ed obousm\u011brn\u011b?<\/summary>\n<p>U integra\u010dn\u00ed platformy ano \u2014 ka\u017ed\u00e1 agenda m\u00e1 sv\u016fj sm\u011br a interval. Typicky: z\u00e1kazn\u00edci obousm\u011brn\u011b, faktury z POHODY do CRM, objedn\u00e1vky z CRM do POHODY. Nativn\u00ed dopl\u0148ky b\u00fdvaj\u00ed jednosm\u011brn\u00e9.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Mus\u00edm kv\u016fli integraci kupovat mServer?<\/summary>\n<p>mServer nen\u00ed samostatn\u00fd produkt \u2014 je sou\u010d\u00e1st\u00ed ka\u017ed\u00e9 POHODY. Je ale pot\u0159eba ho u v\u00e1s zprovoznit a udr\u017eet v b\u011bhu; s t\u00edm pom\u016f\u017eeme. U edic SQL a E1 um\u00edme \u010d\u00e1st p\u0159enos\u016f \u0159e\u0161it i p\u0159\u00edmo p\u0159es datab\u00e1zi.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>M\u00e1m jin\u00e9 CRM ne\u017e Raynet \u2014 jde to taky?<\/summary>\n<p>Ano. Postup je stejn\u00fd pro libovoln\u00e9 CRM s API (Pipedrive, HubSpot a dal\u0161\u00ed) \u2014 m\u011bn\u00ed se jen strana CRM, strana POHODY z\u016fst\u00e1v\u00e1. Kombinace najdete v <a href=\"\/cs\/systemy-integrace\/\">katalogu integrac\u00ed<\/a>.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":"<p>Obchod \u017eije v CRM, \u00fa\u010detnictv\u00ed v POHOD\u011a \u2014 a mezi nimi se p\u0159episuje. Co se mezi syst\u00e9my p\u0159en\u00e1\u0161\u00ed, jak\u00e9 jsou \u010dty\u0159i cesty propojen\u00ed a na co si d\u00e1t pozor.<\/p>\n","protected":false},"author":0,"featured_media":67157,"template":"","class_list":["post-71571","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie\/71571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie"}],"about":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/types\/erpedie"}],"version-history":[{"count":1,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie\/71571\/revisions"}],"predecessor-version":[{"id":71903,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/erpedie\/71571\/revisions\/71903"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/media\/67157"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/cs\/wp-json\/wp\/v2\/media?parent=71571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}